Keeping App_Browsers/_vti_cnf deleted

We have all probably seen the ruthless message below:
-------------------------------------------------
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Data at the root level is invalid. Line 1, position 1.

Source Error:


Line 1:  <browsers>
Line 2:    <browser refID="safari1plus">
Line 3:  
-------------------------------------------------

Which simply means that the frontpage server extensions has once again added the _vti_cnf folder in the App_Browsers folder of your application on the server.  Deletng this folder clears out the error.  My qestion is, short of running a script ever 60 seconds, is there a clean way of keeping this folder gone or perhaps fixing .net so that it doesn't complain that the folder exists?

Thanks!
jglazer63Asked:
Who is Participating?
 
jglazer63Connect With a Mentor Author Commented:
Well if it comes to removing fp extensions and loosing that ease of use over writing a stupid script that just deletes that folder, i'll write the script.  I just hate that this has been an issue for so long and nobody has come up with a solution.
0
 
Seven priceFull StackCommented:

You just need to deploy your ASPX Pages, the BIN directory, web.config and other static files like XML, JPG etc.,
So, you can avoid them getting into the deployment server.

Also you need to remove the front page extension using IIS, This way it will not happen again.
0
 
jglazer63Author Commented:
Remove FP extensions?  I thought that was the best way to work with IIS an Visual Studio (ie, open Remote web server).  Am I wrong?
0
 
Seven priceFull StackCommented:
No you are correct, This is the best way to use a remote server.  but if you keep having that problem you should remove the extension on the production server
0
 
JGarlandXCommented:
I ran across this today and it took me a while to figure out a solution. I want to keep FP extensions on my sites so here is what I did.

1. Create a blank text file named "_vti_cnf"

2. Delete the _vti_cnf folder

3. Upload the "_vti_cnf" text file.

FrontPage will not be able to create a new _vti_cnf folder because a file of that same name will already exist

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.