G
Guest
Hi,
I need to get a string from a COM component at application start. (It's a
Long Story and I cannot change this fact.) In ASP.NET 1.1, I simply called
this COM component in Global.asax.cs from Application_Start, stuck the string
in the HttpApplication.Application object and life was good.
However, I've noticed in ASP.NET 2.0 you are not given the opportunity to
create a .cs codebehind file for the Global.asax when you go to ADD NEW
ITEM..., the PLACE CODE IN SEPERATE FILE grayed out. I know I can get around
this by manually creating a Global.asax.cs but I'm worried this is creating
some sort of risk.
A) What is the reason for not allowing a code behind file for Global.asax in
ASP.NET 2.0?
B) What would be the best way for my to get my string out of the COM object
at Application_Start – I do not know how do COM interop from a CODE-INSIDE
file because it seems like you can not add the using statement (as in using
MyCOMobj?
Thanks,
Nick
I need to get a string from a COM component at application start. (It's a
Long Story and I cannot change this fact.) In ASP.NET 1.1, I simply called
this COM component in Global.asax.cs from Application_Start, stuck the string
in the HttpApplication.Application object and life was good.
However, I've noticed in ASP.NET 2.0 you are not given the opportunity to
create a .cs codebehind file for the Global.asax when you go to ADD NEW
ITEM..., the PLACE CODE IN SEPERATE FILE grayed out. I know I can get around
this by manually creating a Global.asax.cs but I'm worried this is creating
some sort of risk.
A) What is the reason for not allowing a code behind file for Global.asax in
ASP.NET 2.0?
B) What would be the best way for my to get my string out of the COM object
at Application_Start – I do not know how do COM interop from a CODE-INSIDE
file because it seems like you can not add the using statement (as in using
MyCOMobj?
Thanks,
Nick