Getting rid of these stupid _vti_ folders

Getting rid of these stupid _vti_ folders

am 10.11.2005 16:01:06 von hoenes1

Hi all,

FrontPage 2003 creates some _vti_ folders in every folder on
my website. I find it quite offending that MS implies that the user
will accept this without a word of protest. I don't use any extensions
FP offers, nevertheless does FP create these folders and does not offer
any settings that might disable this "feature". At the moment I've
helped myself out by creating a little tool "vtidelete" which
recursively deletes any directories containing "_vti_". It works, but
it is a dirty workaround. I don't want to remove FP because of its
decent editor features and designer usability. I'm even quite satisfied
with FP's functionality. But these damn _vti_ folders really upset me.
I want to sync the files in my Webserver VM with the files on the
fileserver (from which the files are then copied to the live server by
another application). I've chosen "sync with folder" in FP's remote
website configuration. But there's no option to remove/ignore these
folders (that actually serve no purpose for me). Any input?

Thanks in advance.

Re: Getting rid of these stupid _vti_ folders

am 10.11.2005 16:12:35 von tarowe

You do use the FP extensions during the development of your web, these _vti folders are used by FP
to manage the content within your web / site. MS purchased FrontPage many years ago from Vermeer
Technologies, Inc. (vti).

Also, the _vti folders are never copied/published between location, the FP extensions on the remote
server create and maintain them as needed.

If you don't want the _vti folders, then do not use FP.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

"hoenes1" wrote in message
news:1131634866.882773.52720@g43g2000cwa.googlegroups.com...
> Hi all,
>
> FrontPage 2003 creates some _vti_ folders in every folder on
> my website. I find it quite offending that MS implies that the user
> will accept this without a word of protest. I don't use any extensions
> FP offers, nevertheless does FP create these folders and does not offer
> any settings that might disable this "feature". At the moment I've
> helped myself out by creating a little tool "vtidelete" which
> recursively deletes any directories containing "_vti_". It works, but
> it is a dirty workaround. I don't want to remove FP because of its
> decent editor features and designer usability. I'm even quite satisfied
> with FP's functionality. But these damn _vti_ folders really upset me.
> I want to sync the files in my Webserver VM with the files on the
> fileserver (from which the files are then copied to the live server by
> another application). I've chosen "sync with folder" in FP's remote
> website configuration. But there's no option to remove/ignore these
> folders (that actually serve no purpose for me). Any input?
>
> Thanks in advance.
>

Re: Getting rid of these stupid _vti_ folders

am 10.11.2005 23:48:56 von Andrew Murray

They are required - don't touch them.

They should be hidden folders, so normally you wouldn't know they were there
unless you went digging for them. If you don't want to see them in the file
list, then set the hidden files to "ON" so they won't be shown.

"hoenes1" wrote in message
news:1131634866.882773.52720@g43g2000cwa.googlegroups.com...
> Hi all,
>
> FrontPage 2003 creates some _vti_ folders in every folder on
> my website. I find it quite offending that MS implies that the user
> will accept this without a word of protest. I don't use any extensions
> FP offers, nevertheless does FP create these folders and does not offer
> any settings that might disable this "feature". At the moment I've
> helped myself out by creating a little tool "vtidelete" which
> recursively deletes any directories containing "_vti_". It works, but
> it is a dirty workaround. I don't want to remove FP because of its
> decent editor features and designer usability. I'm even quite satisfied
> with FP's functionality. But these damn _vti_ folders really upset me.
> I want to sync the files in my Webserver VM with the files on the
> fileserver (from which the files are then copied to the live server by
> another application). I've chosen "sync with folder" in FP's remote
> website configuration. But there's no option to remove/ignore these
> folders (that actually serve no purpose for me). Any input?
>
> Thanks in advance.
>

Re: Getting rid of these stupid _vti_ folders

am 11.11.2005 03:11:13 von Wally S

It shouldn't be a problem. It's just something FP uses to manage the files.
Many softwares use special work files or folders that the user does not
touch.

Wally S

"hoenes1" wrote in message
news:1131634866.882773.52720@g43g2000cwa.googlegroups.com...
> Hi all,
>
> FrontPage 2003 creates some _vti_ folders in every folder on
> my website. I find it quite offending that MS implies that the user
> will accept this without a word of protest. I don't use any extensions
> FP offers, nevertheless does FP create these folders and does not offer
> any settings that might disable this "feature". At the moment I've
> helped myself out by creating a little tool "vtidelete" which
> recursively deletes any directories containing "_vti_". It works, but
> it is a dirty workaround. I don't want to remove FP because of its
> decent editor features and designer usability. I'm even quite satisfied
> with FP's functionality. But these damn _vti_ folders really upset me.
> I want to sync the files in my Webserver VM with the files on the
> fileserver (from which the files are then copied to the live server by
> another application). I've chosen "sync with folder" in FP's remote
> website configuration. But there's no option to remove/ignore these
> folders (that actually serve no purpose for me). Any input?
>
> Thanks in advance.
>

Re: Getting rid of these stupid _vti_ folders

am 11.11.2005 08:01:24 von hoenes1

Thanks for all your replies.

Ok, now I see that these folders are intrinsically tied to FP. Maybe we
should adapt our sync tool to ignore hidden folders. Although many
users have turned on hidden and system files to be shown (as all of you
can surely confirm) to have a better overview over the file system. In
addition, these redundant files create an overhead of at least 100% of
the web site's size. Many other softwares allow at least configuring
the location of these "special work files". I'm trying to adapt, but in
the end, there remains a mouldy aftertaste.
Thanks again for your efforts.

Re: Getting rid of these stupid _vti_ folders

am 11.11.2005 14:17:27 von tarowe

If you look at the files within the those folder you will see that they do not equal 100% of the
files they represent.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

"hoenes1" wrote in message
news:1131692484.904943.102300@z14g2000cwz.googlegroups.com.. .
> Thanks for all your replies.
>
> Ok, now I see that these folders are intrinsically tied to FP. Maybe we
> should adapt our sync tool to ignore hidden folders. Although many
> users have turned on hidden and system files to be shown (as all of you
> can surely confirm) to have a better overview over the file system. In
> addition, these redundant files create an overhead of at least 100% of
> the web site's size. Many other softwares allow at least configuring
> the location of these "special work files". I'm trying to adapt, but in
> the end, there remains a mouldy aftertaste.
> Thanks again for your efforts.
>