Avoiding Bin directory with precompiled sites

  • Thread starter Thread starter bosa
  • Start date Start date
B

bosa

Hi,

I am looking for a way to deploy a precompiled ASP.NET site that does
not involve the bin directory.

My problem is that deploying binary files to the bin directory remains
a no-no on several security check-lists and is unacceptable to my
customers.

I tried using the aspnet_merge, signing the assembly with a strong
name. However I could not get the site to work when I moved the
assembly to the GAC.

Does anyone know of a way to make this work?

Regards,

Bo
 
Not sure i understood you correctly.
"looking for a way to deploy a precompiled ASP.NET site that does not
involve the bin directory."

But it though that is what "precompiled" means...
Your aspx pages were compiled into DLLs and you move them to server.

If you do not want to move DLLs then you will have to distribute source
files (.cs and aspx) and let ASP.NET to compile them on a fly.

George
 
Not sure i understood you correctly.
"looking for a way to deploy a precompiled ASP.NET site that does not
involve the bin directory."

But it though that is what "precompiled" means...
Your aspx pages were compiled into DLLs and you move them to server.

If you do not want to move DLLs then you will have to distribute source
files (.cs and aspx) and let ASP.NET to compile them on a fly.

George










- Show quoted text -
Click to expand...

Since the aspnet_merge utility allows strong-naming the assembly, I am
looking for a way to install it in the GAC instead of in the bin
directory

/bo
 
Back
Top