web deployment, dll's and .compiled files...

Is there any way to control the name of the .compiled files to be named
just their own original filenames instead of that GUID/hash name
appended to the end of the file?
What I have been doing seems to be working fine, but I want to make
sure I'm not setting myself up for trouble in the future.
I have been compiling into a non-updateable website and merging to a
single dll and then taking only the dll (after I already once copied
everything) and pasting it into the target bin directory and resetting
IIS. It seems to be working fine, but I am worried that the .compiled
files and the dll have some kind of identity/link to each other and, by
not copying everything (including the .compiled files) and just the
single dll, I am not doing it in such a good way...any thoughts
appreciated. Thank you...If your goal is to have a single assembly for your web project, why not
switch to the Web Application Project type? that's what it does.
http://msdn.microsoft.com/asp.net/r...ap/default.aspx
Peter
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
"Jay" wrote:

> Is there any way to control the name of the .compiled files to be named
> just their own original filenames instead of that GUID/hash name
> appended to the end of the file?
> What I have been doing seems to be working fine, but I want to make
> sure I'm not setting myself up for trouble in the future.
> I have been compiling into a non-updateable website and merging to a
> single dll and then taking only the dll (after I already once copied
> everything) and pasting it into the target bin directory and resetting
> IIS. It seems to be working fine, but I am worried that the .compiled
> files and the dll have some kind of identity/link to each other and, by
> not copying everything (including the .compiled files) and just the
> single dll, I am not doing it in such a good way...any thoughts
> appreciated. Thank you...
>