Then you should also know that this error is persisting because the values given above might be an XSS attack. If you are sure that you want to accept this type of values on your dabatase you may explicitly remove this validation by adding this tag to your page’s masterpage or 1st line of tag.
If you are on ASP .NET MVC you can add this to your model, assuming that your model has the content variable.
[AllowHtml] public string content = String.Empty;
Thanks hope it help you allot. Also if you are not familiar with XSS attacks, I will try to make an article for that so you can create your own script that is hack-able, be able to prevent it, and know what are it’s crons.
I have been modifying a source code from my work and it has been a little difficult to test the system in multiple instances of database.
I have been modifying a source code from my work and it has been a little difficult to test the system in multiple instances of database. This is due the previous developers of the said source code used Inline Query Codes and Connection Strings. In addition to that this Inline Queries and even their Stored Procedure use Inline Database, an example is [Database1].[dbo].[tbl_tableName] which should not be in practice if it is using the same database on the whole coding system.
This kind of practice limits the system to use different database name. For an instance you have a web server that serves both Development and Production Environment. You have a project that needs to have Dev and Prod on the said server. If this practice is used you are limited to one Environment at a time nevertheless you modify each script to change that inline database name. So its better to use [dbo].[tbl_tableName] than [Database1].[dbo].[tbl_tableName]
This is a system that I have developed for a seminary, San Carlos Seminary, at Guadalupe here at Manila. I was given this privilege by my classmate, Eissa Bedural, who has a brother, Kuya Edric Bedural, studying at the said seminary.