I had a data string that used “<w>” as the delimiter passed into a javascript function from an event handler in HTML, and that was totally legal in .NET Framework 3.5. However, .NET Framework 4.0 detected that as a potentially dangerous value. By changing the delimiter to a string without the angle brackets, I stopped getting the run-time error. I thought that was a good improvement made in .NET 4.0.
-
Recent entries
- cshtml files getting 404 error after posted to IIS 7
- How to change authentication in IIS using C#
- iOS5 whitelist URL unauthorized using PhoneGap
- vsdbcmd.exe fails with error 0x8007000B
- vsdbcmd.exe gets blocked by its calling process
- Project not selected to build for this solution configuration
- A potentially dangerous Request.Form value was detected from the client
- SQLCMD Mode
- TFS Error MSB4062
- The working folder [source path] is already in use by the workspace [workspace name];[owner] on computer [tfs server].
-
Browse popular tags
.net framework 4.0 artificial intelligence asp.net authentication c# f# IIS ios 5 msbuild mvc phonegap sql server 2008 tfs visual studio 2010 vsdbcmd webmatrix windows forms -
Meta