June 2010 Entries
One of the changes in asp.net 4.0 that I discovered the hard way last week has to do with request validation. I created a web service with a few methods that allow an application to send email messages using an email marketing service instead of our SMTP server, very simple nothing complex.
The problem
We can call and execute the web methods from our web application without a problem, everything works. However, when we tried to execute one of these web methods where the message's body is a parameter, and we executed it from a browser using query strings we got...
It happens to all of us, unfortunately the reason you are reading this is probably because it is happening to you now.
Let's say that your boss comes in one morning and asks you to work in a project, then he mentions you need to get it from Visual SourceSafe (VSS)... you think is a joke until you noticed that your boss has that "serious" look in his face. F*ck. Or maybe you receive the project in a compressed file and when you try to open it, you realize this project was under Visual Source...
This might be something you already know, however I just found out about it and I am writing it down to share it with you and to help myself find it in case I forget about it which will probably happen.
In the past, when working with Visual Studio projects downloaded from the web, or projects that are shared with other developers, every once in a while I ran into the issue of not being able to load the project in Visual Studio because either the path is wrong, or if it is a web project, maybe the project is setup...