dynamically changing assembly
-
Hi everyone, I was asked following question, if anyone knows can u pls tell me 1. The assembly has been updated from version 1.0 to 2.0. The latest assembly 2.0 has some problem, it is required that application should use old assembly. How can we make the application to use old versioned assembly dynamically? 2. while developing a web application what factors should be considered with respect to no of ppl access the same application at a time? 3. When a http request is received by IIS serever, it checks if the page is .aspx and passes to aspnet_is.dll engine. How IIS server detects aspx page? if I have a .html page, and I change the file extension to .aspx, will this page process by IIS server to aspnet_is.dll? Thanks and regards
-
Hi everyone, I was asked following question, if anyone knows can u pls tell me 1. The assembly has been updated from version 1.0 to 2.0. The latest assembly 2.0 has some problem, it is required that application should use old assembly. How can we make the application to use old versioned assembly dynamically? 2. while developing a web application what factors should be considered with respect to no of ppl access the same application at a time? 3. When a http request is received by IIS serever, it checks if the page is .aspx and passes to aspnet_is.dll engine. How IIS server detects aspx page? if I have a .html page, and I change the file extension to .aspx, will this page process by IIS server to aspnet_is.dll? Thanks and regards
Job interview? Doesn't the fact that you're asking the CodeProject forums give away you might be cheating a bit? Here are my guesses. 1. With enormous difficulty unless there's something I don't know. There's no way to unload an assembly, you have to unload the AppDomain to which it has been loaded, so unless you've really planned for this, you can't unload version 1.0 and load in 2.0. To do that you'd need multiple domains in your app and have a Marshalling nightmare between them all. By design, you could load the assembly in at startup and use reflection to access it, but again you would have had to have planned for this in the design. Anybody know a way of doing this without reflection and I'd be very interested to hear how. 2. Scalability issues. Things like session expiry, caching and the like. Also speed of hardware/farming options etc. 3. IIS knows because you ask for a page with an .aspx extension. In IIS you can tell which ISAPI extensions to use for each file type. If you change an .html page to end with .aspx, then it will get passed to the asp.net ISAPI dll and handled by .net (probably very badly).
Regards, Rob Philpott.