|
Dear All,
After following instruction from the excellent article by Panayotis Matsinopoulos for setting up a multi-language interface -
Allow users to select the user interface language in your ASP.NET Web application
I went to debug it using the built-in debugger in Visual Studio (VS) and received an error that the class module cannot be loaded. I know it is finding the module because if I move it to a different location in my project, it specifies that it cannot find the module.
This got me thinking about the whole subject of httpModules and their deployment on a localhost webserver and also use in VS debugging and I now have the following questions as a new and aspiring .NET programmer -
1. Does using the VS debugger make a difference? Does for example the module need to be registered separately ahead of time somehow on the localhost? Does it make a difference that the web.config file, the class module for the LanguageModule and the page itself (as well as the App_GlobalResources files) are all inside the same VS project?
2. Does the httpModule need to be registered separately on the local IIS for the application? I mean, I'm sure it needs to be so registered if I am running the application in a browser outside of Visual Studio, - but what about from within VS using the debugger? Doesn't the built-in compiler in the Debugger handle this (registration)?
3. If none of the above are issues in using the VS debugger, how can I go about debugging why the module won't load?
Thanks everyone for your assistance. I hope this isn't too much of a newbie question for the esteemed company!
Best Regards,
Ray Fischer, Kibo, Germany
|
|
|
|
|
If you have an issue with a CodeProject article then please first post your question in the forum at the end of the article. In this way the author will be notified of your query.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
Thanks Richard for your answer. I can post it there as well, I was just not sure because this is more of a general question relating to VS and the debugger there and not so much having to do with the method shown.
|
|
|
|