Re: VS.NET How-To

From: Roland Hall (nobody_at_nonononono.us)
Date: 03/02/04 

Date: Tue, 2 Mar 2004 03:57:07 -0600

"Tian Min Huang" wrote:
: >> If I can use VS 6.0 with FPSE on this site, would the FPSE still be an
: issue or possibly an authentication issue in IIS itself, like with ASPNET
: user?
:
: I'm sorry that I am not familiar with Visual Interdev 6.0 very much. As in
: this case, I belive that FPSE may not be installed or configured properly.
: You can ask your web host to re-install or config FPSE as described in the
: following KB article:
:
: HOW TO: Configure FrontPage Server Extensions in Internet Information
: Services
: http://support.microsoft.com/default.aspx?scid=kb;EN-US;298158

Hi...

I wrote the web host and they responded with, "We're currently not
supporting VS.NET 2K3 yet. Perhaps sometime in the future." I wrote back
and politely encouraged them put forth a little effort since it's VS.NET 2K3
and it's currently March 2004. I also sent them the links you provided with
an inclusion of something else I found on the net. I think it was from
expert-exchange.

     Accepted Answer from Dra***
      Date: 12/18/2003 07:21AM PST
     Accepted Answer

      If you install the .NET Framework on a system that has IIS already
installed, IIS is automatically configured to handle requests to ASP.NET
pages, and to redirect the execution to the ASP.NET runtime. However, it may
happen that you installed the framework on a Windows 2000 Professional
system where IIS was not already present, and just later decided to add IIS.
Registering ASP.NET on IIS is not just a matter of associating the various
.aspx, .asmx, .axd, .ashx and the other ASP.NET extensions to the
aspnet_isapi.dll ISAPI, more has to be done to create the ASP.NET account
and to set it for ASP.NET requests, register the ISAPI itself and other
stuff. Doing all this manually can be a difficult operation, and requires a
good understanding of many details. Fortunately there is an utility, shipped
with the .NET Framework but not documented, that can take care of these
configuration chores for you. The utility is aspnet_regiis.exe, it is
located under %WindowsDir%\Microsoft.NET\Framework\vx.y.zzzz\ and you should
call it with the -i parameter: aspnet_regiis.exe -i

We'll see what happens.

I have another issue with them also where they're still using
http://username:password@www.domain.com and they have already applied the
update that renders this useless unless you make some changes to your setup.
They responded with the link to the article. I told them, "Ok, now read the
whole article and make the necessary changes so my control panel works like
it should or modify the control panel so it will request me to type in my
credentials." I'm wondering if the real support team is all on vacation and
perhaps the owner's, out of work, pizza deliverin' nephew is at the console.