How to install VSTS Beta 2 on remote development Win2003 Server?

Hot Topic

ReportViewer error
Where do I place text for a captionId?
grid width
VS2005 Pro Install problem
Problem with multiple datasets & reportViewer
Use of OperationContext.Current for duplex
Problem DownLoad File
Assembly problem!
If I only work with Access Databases, what should I purchase
help..!!Error when install VS 2005

Visual Studio

Set up VSS so all files checked in before final release
Soap security negotiation failed
Where to get help? "umpnpmgr.dll error"
Msbuild and TlbImp from Sdk 1.1
Excel file
mscorsvw.exe
Access/Create DOM for MailItem.HTMLBody and Open Contact by EntryID
Word Template crash
Word.Docs in VB.Net
display subreport data in a status box

How to install VSTS Beta 2 on remote development Win2003 Server?

I installed VSTS Beta 2 on remote web development Win2003 Server (I selected none of the VSTS components). Prior to doing that I uninstalled VS beta 1 succesfully.

The installation was successfull, but now the ASP.NET tab is missing from IIS 6 web site properties, and I have no way setting the script mappings for spesific Framework version. I tried -regiis -ir -enable, but the tab is still missing.

Any advice how to do a remote development server installation (.NET Framework 2 and ASP.NET 2 Beta 2) properly



Answer this question

How to install VSTS Beta 2 on remote development Win2003 Server?

  • Spog Mog

    Worked for me as well on my Win 2000 Server.

  • The Aqua

    Thanks , it did it for me to !!! You're the best !!!

  • almargob

    thanks, works for me too \o/

  • ivanwong

    Thanks, that fixed it on my machine too.

    --Oren

  • ztc

    Thanks, that did the trick.

    With regiis I was just trying to do a quick fix and get the tab back using -enable.

    BTW, do you know if I can still use the AccessMembershipProvider The only option seems to be SqlMembershipProvider, and I didn't install SQL Server 2005 Beta that came with VSTS Beta 2.

  • vludyeidiet

    Hey~

    This is a problem caused by the change between Beta 1 and Beta 2.  I have ran into it on a few occasions now - tedious but easy to fix.

    To fix, check the following 3 regkeys -
    HKEY_CLASSES_ROOT\CLSID\{7D23CCC6-A390-406E-AB67-2F8B7558F6F6}\InprocServer32

    HKEY_CLASSES_ROOT\CLSID\{FD5CD8B1-6FE0-44F3-BBFB-65E3655B096E} \InprocServer32

    HKEY_CLASSES_ROOT\CLSID\{FEDB2179-2335-48F0-AA28-5CDA35A2B36D}\InprocServer32

     
    Under (expand) InProcServer32, look for the presence of a non-2.0.0.0 (example 2.0.36.0) and remove it.  It has a reference that causes this to bust. (in my example, it was under the CLSID FD5C with a setting 2.0.36 ...)

    However, as to your question, you are not stuck if you do not have this MMC interface.  You can use aspnet_regiis.exe but you were using the wrong switch -

    aspnet_regiis -s <path> where path equals the location in the metabase where you want the mappings to change.

    Note:  There is also a switch to do this non-recurvisely if you desire.

    Thanks,
    ~Chris Adams
    Web Platform Supportabilty Lead


  • How to install VSTS Beta 2 on remote development Win2003 Server?
Answer this question