No, not must..just one way.
Reverse-engineer what the Copy Project feature does.
Jeff
wait,
it is possible to just copy over files from one directory to the ASP.NET app
deployment dir. This will "deploy" the app. You can use VS to do this, or
xcopy, or drag-n-drop from explorer, Or a perl script, or whatever. It's
just copying.
What the original poster was asking about was the JIT-compiling of ASPX and
ASMX files, I suppose. When this happens, the aspnet worker process
actually preprocesses the ASPX or ASMX, then launches csc.exe (or vbc.exe,
etc) and compiles the code into a new DLL, randomly named. The random name
is making Black Ice cough, according to the OP. This is part of the ASP.NET
model for v1.1 and cannot be changed.
For ASP.NET v2.0 ("Whidbey"), there is a possibility to "pre-compile"
websites. This may address your needs. But for v1.1, you will always get
randomly-named DLLs when you include any ASPX or ASMX files in your web app.
-Dino
> No, not must..just one way.
>
[quoted text clipped - 74 lines]
>> > >
>> > > ________________________________________