crispelzer
MIS
I would much like to be able to use the NavBar DTC in VI but each time that I view the page in my browser there appears [FrontPage vinavbar component] where the control should appear. There seems to be some incompatibility between the extensions currently enabled on my IIS and the authoring tool (VI) that is attempting to exploit them.
I've searched a few different forums looking for information on this topic and have yet to come upon any helpful suggestions. Please continue.
My Config:
My OS is WinXP, the web server is IIS 5.1 I too am using Visual Interdev which was installed along with other apps included in Visual Studio 6.0
My PC is acting as both client and server.
To my knowledge PWS (Personal Web Server) is not included with Windows XP.
I had previously installed FrontPage 2002 on this machine and still have it, though I would much prefer to develop w/ VI.
The following directories are visible from Windows Explorer:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\40\BOTS\VINAVBAR
C:\Program Files\Common Files\Microsoft Shared\web server extensions\50\bots\vinavbar
According to the MSDN
The text [FrontPage VINavbar Component] appears in place of navigation bar links if you do not have the proper server components installed on both your local machine and the master Web server. To use the PageNavbar control, you must have the VINavbar component installed on your local machine and on the master Web server. The VINavbar component is installed with the Microsoft® FrontPage® 98 server extensions.
MSDN further states
On your local machine, search for the vinavbar folder. The vinavbar folder is installed by default in drive:\Program Files\Microsoft FrontPage\version3.0\bots\.
My local machine is also my server but nevertheless I confirmed that the following path is a valid one on my PC:
C:\Program Files\microsoft frontpage\VERSION3.0\bots\vinavbar
I also noticed that in each of these respective vinavbar folders there exists .dll's certain version numbers. I've learned that basically the FrontPage 98 Server Extensions version number begins with 3, 2000 sever extensions version number begins with 4, and the 2002 server extenion version number begins with 5.
So thinking that clearly this was a case of simply having to run, or enable, the 98 Server Extensions on my IIS I proceeded to copy the VERSION 3.0 folder that I mentioned above into the web server extensions folder resulting in the following path:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\VERSION3.0
Now the question is how to determine which version of the server extensions are actually enabled on my IIS.
I thought the following was particularly cursious: If I check the server extensions version from within VI I am told that it is version 4.0.5322
However if I view the very same web thru FrontPage by clicking on Tools --> Web Settings I'm told that the server extensions version is 5.02.2623
And this at the root web so I assume that this is consistent with all subwebs.
So according to VI I have the 2000 server extensions enabled. According to FrontPage I have the 2002 server extensions enabled. Due to the error message I receive [FrontPage vinavbar component] every time I attempt to use a NavBar DTC I'm convinced that there is some incompatibility, but I do not know where or how to resolve it.
I believe that with Visual Studio 6.0 the Frontpage 98 Server Extensions are installed on the local machine, presumably at
C:\Program Files\microsoft frontpage\VERSION3.0
How then do I enable those 98 extensions thru the IIS? I've noticed that there only exist a MMC snap-in at
C:\Program Files\Common Files\Microsoft Shared\web server extensions\40\BIN\fpmmc.msc
Why would there only be a MMC snap-in for the 2000 version??
Why is there no snap-in for the 2002 directory? There is no fpmmc.msc file at this location.
I apologize for being long-winded but this is bit frustrating. Finally, I have these questions:
Is is possible that I have all three versions of the FrontPage server extensions installed on this machine?
If so, is it possible to elect to enable one version rather than another? Or is the later version used by default, requiring that I uninstall the 2000 and/or 2002 version if I want to enable the 98 server extensions?
Is the error message [FrontPage vinavbar component] due to the fact that VI wants to use the 98 server extensions but they are not currently enabled on my IIS?
If so, how do I enable that version? And is it possible that by doing so I would forfeit the ability to use some other DTC, such as a data-bound DTC?
Perhaps Windows XP (and by extension the IIS 5.1) is not compatible with the 98 Server Extensions anyway...
If you have any useful information concerning this problem I would very much appreciate your sharing it with me. I promise to in turn share it with those other poor souls lost wandering the wilderness of FrontPage Server Extensions.
Thanks,
crispelzer
I've searched a few different forums looking for information on this topic and have yet to come upon any helpful suggestions. Please continue.
My Config:
My OS is WinXP, the web server is IIS 5.1 I too am using Visual Interdev which was installed along with other apps included in Visual Studio 6.0
My PC is acting as both client and server.
To my knowledge PWS (Personal Web Server) is not included with Windows XP.
I had previously installed FrontPage 2002 on this machine and still have it, though I would much prefer to develop w/ VI.
The following directories are visible from Windows Explorer:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\40\BOTS\VINAVBAR
C:\Program Files\Common Files\Microsoft Shared\web server extensions\50\bots\vinavbar
According to the MSDN
The text [FrontPage VINavbar Component] appears in place of navigation bar links if you do not have the proper server components installed on both your local machine and the master Web server. To use the PageNavbar control, you must have the VINavbar component installed on your local machine and on the master Web server. The VINavbar component is installed with the Microsoft® FrontPage® 98 server extensions.
MSDN further states
On your local machine, search for the vinavbar folder. The vinavbar folder is installed by default in drive:\Program Files\Microsoft FrontPage\version3.0\bots\.
My local machine is also my server but nevertheless I confirmed that the following path is a valid one on my PC:
C:\Program Files\microsoft frontpage\VERSION3.0\bots\vinavbar
I also noticed that in each of these respective vinavbar folders there exists .dll's certain version numbers. I've learned that basically the FrontPage 98 Server Extensions version number begins with 3, 2000 sever extensions version number begins with 4, and the 2002 server extenion version number begins with 5.
So thinking that clearly this was a case of simply having to run, or enable, the 98 Server Extensions on my IIS I proceeded to copy the VERSION 3.0 folder that I mentioned above into the web server extensions folder resulting in the following path:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\VERSION3.0
Now the question is how to determine which version of the server extensions are actually enabled on my IIS.
I thought the following was particularly cursious: If I check the server extensions version from within VI I am told that it is version 4.0.5322
However if I view the very same web thru FrontPage by clicking on Tools --> Web Settings I'm told that the server extensions version is 5.02.2623
And this at the root web so I assume that this is consistent with all subwebs.
So according to VI I have the 2000 server extensions enabled. According to FrontPage I have the 2002 server extensions enabled. Due to the error message I receive [FrontPage vinavbar component] every time I attempt to use a NavBar DTC I'm convinced that there is some incompatibility, but I do not know where or how to resolve it.
I believe that with Visual Studio 6.0 the Frontpage 98 Server Extensions are installed on the local machine, presumably at
C:\Program Files\microsoft frontpage\VERSION3.0
How then do I enable those 98 extensions thru the IIS? I've noticed that there only exist a MMC snap-in at
C:\Program Files\Common Files\Microsoft Shared\web server extensions\40\BIN\fpmmc.msc
Why would there only be a MMC snap-in for the 2000 version??
Why is there no snap-in for the 2002 directory? There is no fpmmc.msc file at this location.
I apologize for being long-winded but this is bit frustrating. Finally, I have these questions:
Is is possible that I have all three versions of the FrontPage server extensions installed on this machine?
If so, is it possible to elect to enable one version rather than another? Or is the later version used by default, requiring that I uninstall the 2000 and/or 2002 version if I want to enable the 98 server extensions?
Is the error message [FrontPage vinavbar component] due to the fact that VI wants to use the 98 server extensions but they are not currently enabled on my IIS?
If so, how do I enable that version? And is it possible that by doing so I would forfeit the ability to use some other DTC, such as a data-bound DTC?
Perhaps Windows XP (and by extension the IIS 5.1) is not compatible with the 98 Server Extensions anyway...
If you have any useful information concerning this problem I would very much appreciate your sharing it with me. I promise to in turn share it with those other poor souls lost wandering the wilderness of FrontPage Server Extensions.
Thanks,
crispelzer