Last week I ran into a wall while developing email capabilities for a .NET project that I am working on. The problem? The code was correct. The web.config configuration was correct. Even most of the iis 6 virtual smtp service was configured correctly since classic asp code was emailing quite happily.
What was the problem?
After consulting with other developers in the Zekiah developer's list, they told me to check for permissions. Once I was put on the right direction, I found an entry with the solution to my specific problem.
I got this weird error when I was trying to regenerate a designer page:
Unable to convert to web application because the code-behind ".*" is missing
The crazy thing was that the code-behind file was there. The only thing that was missing was the designer page.
The solution was to rename the file. As soon as I renamed it, the designer page was generated. Then I renamed it back to its original name. Done :)
Hmm, the long, exciting description on this error that I had written was erased with a firebug crash. So here is the quick hurried version.
After a lot of troubleshooting why I got a null value from a Request parameter, I figured out that the ProcessRequest() was being executed twice. I looked at some pages, and they said that it could be connected with authentication; I followed some of their solutions, but nothing.
The problem: your data has ampersands (&) in it, but you must submit it as a query string to your asp dot net app. After you have sent it, however, the string is truncated at the & character.
The solution: HttpUtility.URLEncode/.URLDecode to send query strings that contain ampersands as data.
The story:
Okay, here is one that gets me all the time, and which I have to look for the solution all the time.
To regenerate the designer page
1. Delete your bogus deisgner.cs page
2. Right click on the aspx file, and select Convert to Web Application
The solution is found in the link below, by John Q. Smith
http://social.msdn.microsoft.com/forums/en-US/csharpide/thread/128202d7-...