_vti_cnf

[Arpan]

Why does ASP create a directory named _vti_cnf containing all the files of
an application for each application? Can deleting those directories
permanently cause some problems?

Thanks,

Arpan

[Tom Kaminski [MVP]]

"Arpan" <ar******@hotmail.com> wrote in message
news:eT**************@tk2msftngp13.phx.gbl...

Why does ASP create a directory named _vti_cnf containing all the files of
an application for each application? Can deleting those directories
permanently cause some problems?

It doesn't - the FrontPage Server Extension do that. They are used to
manage the project. If you delete them, you will have problems with the
FrontPage Server Extensions - which are used by both the FrontPage client
and Visual Interdev.

--
Tom Kaminski IIS MVP
http://www.iistoolshed.com/ - tools, scripts, and utilities for running IIS
http://mvp.support.microsoft.com/
http://www.microsoft.com/windowsserv...y/centers/iis/

[Arpan]

Thanks,Tom, for your reply. What are these FrontPage Server Extensions? Also
what problems may arise with the FrontPage Server Extensions if those
folders are deleted permanently? I neither use FrontPage nor Visual Interdev
to create ASP applications. So can deleting the _vti_cnf folders still
create any problems while executing my ASP applications?

Thanks once again,

Regards,

Arpan

"Tom Kaminski [MVP]" <tomk (A@T) mvps (D.O.T) org> wrote in message
news:bm**********@kcweb01.netnews.att.com...

"Arpan" <ar******@hotmail.com> wrote in message
news:eT**************@tk2msftngp13.phx.gbl...

Why does ASP create a directory named _vti_cnf containing all the files of an application for each application? Can deleting those directories
permanently cause some problems?
It doesn't - the FrontPage Server Extension do that. They are used to
manage the project. If you delete them, you will have problems with the
FrontPage Server Extensions - which are used by both the FrontPage client
and Visual Interdev.

--
Tom Kaminski IIS MVP
http://www.iistoolshed.com/ - tools, scripts, and utilities for running

IIS http://mvp.support.microsoft.com/
http://www.microsoft.com/windowsserv...y/centers/iis/

[Tom Kaminski [MVP]]

"Arpan" <ar******@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

Thanks,Tom, for your reply. What are these FrontPage Server Extensions? Also what problems may arise with the FrontPage Server Extensions if those
folders are deleted permanently? I neither use FrontPage nor Visual Interdev to create ASP applications. So can deleting the _vti_cnf folders still
create any problems while executing my ASP applications?

The server extensions are primarily a way for FP and VI to connect to the
web server for authoring web pages. They also offer some project/site
management features as well as some programming components designed for
novice FrontPage users. As with most other things, MSDN is a good source
for more information:
http://msdn.microsoft.com/library/en...tml/fpovrw.asp.

The "_vti" folders are completely unrelated to ASP - there will be no effect
on ASP if you delete them. The best way, or course, is to simply remove the
extensions from the server if they won't be used (right click on the web
site in the IIS MMC and there should be options to get you there).

--
Tom Kaminski IIS MVP
http://www.iistoolshed.com/ - tools, scripts, and utilities for running IIS
http://mvp.support.microsoft.com/
http://www.microsoft.com/windowsserv...y/centers/iis/

[Bob Barrows]

Arpan wrote:

Thanks,Tom, for your reply. What are these FrontPage Server
Extensions? http://sciris.shu.edu/Manuals/FrontP...k/ovwhatar.htm
Also what problems may arise with the FrontPage Server
Extensions if those folders are deleted permanently? I neither use
FrontPage nor Visual Interdev to create ASP applications. So can
deleting the _vti_cnf folders still create any problems while
executing my ASP applications?

http://webmaster.iu.edu/tool_guide_info/FPprocon.shtml
http://www.maximumasp.com/maxtrack/a...print&kbid=470
http://support.microsoft.com?kbid=281532

I have seen people claim that there is no problem deleting them if you don't
use FP or VID, but I think your best bet is to leave them there. It's not as
if they're taking up a lot of space.

--
HTH,
Bob Barrows - ASP MVP
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[Chris Barber]

Unless you need to use a web authoring tool connecting through the web
server (IIS) instead of accessing the pages directly on disk then you can
delete everything except your website files (unless you have used some of
the FP server extension components such as hit counters, themes etc.).

The *best* way to remove them is to remove Front Page Server extensions from
that web site / subweb (see the IIS MMC Management Console if on W2K or XP)
but *always* take a copy and ensure that your changes (eg. removal) haven't
affected your site. You take this action at your own risk of course.

They [the folders etc.] are there to support accessing the relevant DLLs
required to upload new content etc., provide locking information for the
pages whilst multiple users may be developing against the site, and also
provides a few freebie bits and pieces like themes, page hit counters, site
search tools etc.

Chris.

"Bob Barrows" <re******@NOyahoo.SPAMcom> wrote in message
news:Ou**************@TK2MSFTNGP11.phx.gbl...

Arpan wrote:

Thanks,Tom, for your reply. What are these FrontPage Server
Extensions? http://sciris.shu.edu/Manuals/FrontP...k/ovwhatar.htm
Also what problems may arise with the FrontPage Server
Extensions if those folders are deleted permanently? I neither use
FrontPage nor Visual Interdev to create ASP applications. So can
deleting the _vti_cnf folders still create any problems while
executing my ASP applications?

http://webmaster.iu.edu/tool_guide_info/FPprocon.shtml
http://www.maximumasp.com/maxtrack/a...print&kbid=470
http://support.microsoft.com?kbid=281532

I have seen people claim that there is no problem deleting them if you don't
use FP or VID, but I think your best bet is to leave them there. It's not as
if they're taking up a lot of space.

--
HTH,
Bob Barrows - ASP MVP
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[Bob Barrows]

Chris Barber wrote:

Unless you need to use a web authoring tool connecting through the web
server (IIS) instead of accessing the pages directly on disk then you
can delete everything except your website files (unless you have used
some of
the FP server extension components such as hit counters, themes etc.).

That was the main reason I recommended leaving them. They're not hurting
anything by their presence, and deleting them may break something that uses
them.

--
HTH,
Bob Barrows - ASP MVP
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[Chris Barber]

I agree although I have found occasion to delete them example when copying a
series of HTML pages developed in Visual Interdev for use in a stand alone
VB application. It is also of use where posting a large HTML site to a non
FP extensions enabled internet webserver across a slow 56kbps dial-up is
required.
It is fiddly and can result in losing pages by accident.
The main reason for my response was to explain why they are there in the
first place and the possibility that they can be removed without causing
problems. I'm not advocating deleting them, merely providing information for
the original poster to consider if necessary.

Cheers,

Chris.

"Bob Barrows" <re******@NOyahoo.SPAMcom> wrote in message
news:e3**************@TK2MSFTNGP10.phx.gbl...
Chris Barber wrote:

Unless you need to use a web authoring tool connecting through the web
server (IIS) instead of accessing the pages directly on disk then you
can delete everything except your website files (unless you have used
some of
the FP server extension components such as hit counters, themes etc.).

That was the main reason I recommended leaving them. They're not hurting
anything by their presence, and deleting them may break something that uses
them.

--
HTH,
Bob Barrows - ASP MVP
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[Arpan]

Many many thanks Chris, Bob & Tom for your explanations :)

Regards to all of you,

Arpan

"Chris Barber" <ch***@blue-canoe.co.uk.NOSPAM> wrote in message
news:e5**************@TK2MSFTNGP11.phx.gbl...

I agree although I have found occasion to delete them example when copying a series of HTML pages developed in Visual Interdev for use in a stand alone
VB application. It is also of use where posting a large HTML site to a non
FP extensions enabled internet webserver across a slow 56kbps dial-up is
required.
It is fiddly and can result in losing pages by accident.
The main reason for my response was to explain why they are there in the
first place and the possibility that they can be removed without causing
problems. I'm not advocating deleting them, merely providing information for the original poster to consider if necessary.

Cheers,

Chris.

"Bob Barrows" <re******@NOyahoo.SPAMcom> wrote in message
news:e3**************@TK2MSFTNGP10.phx.gbl...
Chris Barber wrote:

Unless you need to use a web authoring tool connecting through the web
server (IIS) instead of accessing the pages directly on disk then you
can delete everything except your website files (unless you have used
some of
the FP server extension components such as hit counters, themes etc.).
That was the main reason I recommended leaving them. They're not hurting
anything by their presence, and deleting them may break something that

uses them.

--
HTH,
Bob Barrows - ASP MVP
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.