Hi Bragadiru,

Welcome to the MSDN newsgroup.

As for the first question about the global.asax file not get copied when we
precompile the website with "non-updatable" option, it is because the whole
global.asax file's class has been compiled into the App_global.asax.dll
assembly you mentioned. And since global.asax file is a internal used
component (only be request and loaded by ASP.NET runtime rather than
client-side users), so there is no need to put it in the application's
actual directory.   When we choose the "updatable" option when
precompiling, since it dosn't generate the complete global class, so it
will still copy the global.asax file in the target directory so that the
global class can get compiled dynamically at runtime.

As for the second question, this is due to the new dynamic compilation
model of the ASP.NET 2.0 application. Since all the final assemblies are
the dynamic compiled one(which sources from both aspx file and our code
behind), so the assembly version info can not be simply put in codebehind
or other assembly file like 1.1.  Regarding on this, the ASP.NET dev team
is developing a new deployment project which help provide more functions
for customizing the dynamic compiled assemblies of ASP.NET 2.0 web
application. And it include specifying version number for the application's
assembly. You can have a look to see whether it helps:

#Visual Studio 2005 Web Deployment Projects
http://msdn.microsoft.com/asp.net/reference/infrastructure/wdp/

Regards,

Steven Cheng
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.