Instructions for running Visual Studio Code Name "Orcas"

1>Download and Install Microsoft Virtual PC 2004/2007 on your local machine

Download Link: Click here

2>Also download all the following files to your local machine (VSJan2007CTP.part01.exe, VSJan2007CTP.part02.rar, VSJan2007CTP.part03.rar, VSJan2007CTP.part04.rar, VSJan2007CTP.part05.rar, VSJan2007CTP.part06.rar, VSJan2007CTP.part07.rar, VSJan2007CTP.part08.rar, VSCTPBase.exe)

Download Link: Click here

3>Execute VSCTPBase.exe and extract corresponding files (Base01.vhd, Base01.vmc)

4>Execute VSJan2007CTP.part01.exe and extract corresponding files (VSDec2006CTP.vhd, VSDec2006CTP.vmc)

5>Open Microsoft Virtual PC and do the following:

a>Click 'New? and click 'Next'

b>Select 'Add an existing Virtual machine? in Step 2 (options) of the wizard

c>Browse to the folder where VSDec2006CTP.vmc was extracted and click ?Next?

d>Uncheck 'When I click ?Finish open Settings' and click 'Finish'

e>Select the newly created virtual machine from the list and click 'Start'

f>If prompted with a massage 'Base01.vhd has been moved or deleted?, select Configuration and select Base01.vhd extracted in Step 1 (By Default, it looks for Base01 in a different directory)

g>Once virtual machine is started, login with Administrator Login with the following credentials:

Username: Administrator
Password: P2ssw0rd

Vikram

DiscountASP.NET
www.DiscountASP.NET

 

I'd recommend holding off on the Jan CTP...
Scott noted the Feb CTP will be radically different and there will be both an image and install version this time.
The Jan CTP doesn't have these goods in it either:
http://weblogs.asp.net/scottgu/archive/2007/02/08/my-first-look-at-orcas-presentation.aspx

 

Update...
The Visual Studio "Orcas" February CTPwill be available to the general public at the end of February.
A link to download it will be posted on this forum once its available.
It has a tentative release date of February 28, 2007.

Visual Studio (Orcas) CTPs
http://forums.asp.net/1112/ShowForum.aspx





Per Jim Bresler (MSFT ASP.NET Team)
The Orcas February CTP is the first release of Orcas where you will be able to download and play with some the new Orcas web features. It contains some great functionality that I think you will love.
There areso many new featurse I've described just a couple of them!


New Web Designer


The Orcas February CTPincludes a new web designer that replaces the old IE-based designer with one based on FrontPage technology. Work to integrate the web designer from Expression Web Designer began almost two years ago in November 2004. It has tons of new features that include:


1. Full WYGWIG HTML editor that uses the same technology as Expression Web Designer


2. Extensive CSS tools


3. Support for nested master pages


4. Split view<O></O>


5. Unified undo/redo stack that remembers operations in all views.


For screenshots and more information about the new designer, see this post on Mikhail Arkipov?s blog.


Multitargeting


Visual Studio "Orcas" February CTP allows you to develop websitesand projects targeting multiple versions of the .NET Framework. With multitargeting, you can develop web sites using anOrcas CTP and deploy them to servers running .NET Framework 2.0. If you upgrade.NET Framework on yourservers, your websites caneasily target the new framework and access the new features. Intellisense, references, and the debugger will automatically adjust to the version you select a new Framework version.


Javascript Intellisense


The new February CTP takes Javascript support to the next level by supporting Javascript Intellisense.


Summary


The Visual Studio "Orcas" February CTP includes several major features for web development including a new web designer, extensive CSS tools, creating websites and projects that target multiple versions of the .NET framework, and Javascript Intellisense.

 

Another update...Installed the Install version, running fine, VS 2005 Pro running fine also.
Awesome, simply awesome.

Had to run the install twice, actually Maintenance Mode the second time after a fresh boot.
It appears to have taken care of everything.

When you open a Web Site it will ask if you want to convert the site to ASP.NET 3.5
If you answer Yes it will modify the web.config to compile with WinFX.

<system.codedom>
<compilers>
<compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CSharp.CSharpCodeProvider,System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
</compiler>
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" compilerOptions="/optioninfer+">
<providerOption name="CompilerVersion" value="v3.5"/>
</compiler>
</compilers>
</system.codedom>

 

Microsoft Pre-release Software Visual Studio Code Name 'Orcas' - March Community Technology Preview Available

Link to download:


Downlod here

Vikram

DiscountASP.NET
www.DiscountASP.NET

 

I just downloaded and installed codename 'Orcas' the other day, and decided to give it a try with my existing website hosted on DiscountASP.net.

As I was pubishing, it asked me if I wanted to update the FrameWork to version 3.5 (beta), and I clicked 'Yes'.

The site doesn't work now, looks like errors in the Web.Config file.

The feature that I was hoping would be available on 'Orcas' was not (working with MS Access 2007 with the built in data tools on the hosted site through the IDE), so I am looking to revert to my previous development environment (Web Developer Express, MS).

Any ideas on how I may undo the changes I made so that the site works again?

Thank you.

 

As mentioned in my previous post, I kinda figured that much out.

I'm trying to work past this dilemna however.. any ideas?

thanks

 

Thank you for assisting.

Here's the web.config file,







<configuration>


<configSections>


<sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">


<sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">


<section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>


<sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">


<section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere"/>


<section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>


<section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>


<section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/></sectionGroup></sectionGroup></sectionGroup></configSections><appSettings/>


<connectionStrings/>


<system.web>





<compilation debug="false">


<assemblies>


<add assembly="System.Core, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>


<add assembly="System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/></assemblies></compilation>





<authentication mode="Windows"/>











<pages>


<controls>


<add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/></controls></pages>


<httpHandlers>


<remove verb="*" path="*.asmx"/>


<add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>


<add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>


<add verb="GET,HEAD" path="ScriptResource.axd" validate="false" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/></httpHandlers>


<httpModules>


<add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/></httpModules></system.web>





<system.codedom>


<compilers>


<compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CSharp.CSharpCodeProvider,System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">


<providerOption name="CompilerVersion" value="v3.5"/></compiler>


<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" compilerOptions="/optioninfer+">


<providerOption name="CompilerVersion" value="v3.5"/></compiler></compilers></system.codedom>





<system.web.extensions>


<scripting>


<webServices>














</webServices></scripting></system.web.extensions>





<system.webServer>


<validation validateIntegratedModeConfiguration="false"/>


<modules>


<add name="ScriptModule" preCondition="integratedMode" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/></modules>


<handlers>


<remove name="WebServiceHandlerFactory-Integrated"/>


<add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>


<add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>


<add name="ScriptResource" verb="GET,HEAD" path="ScriptResource.axd" preCondition="integratedMode" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/></handlers></system.webServer></configuration>


======================================


and here is the error message:


Line 66: <compilers>
Line 67: <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CSharp.CSharpCodeProvider,System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
Line 68: <providerOption name="CompilerVersion" value="v3.5"/></compiler>
Line 69: <compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" compilerOptions="/optioninfer+">
Line 70: <providerOption name="CompilerVersion" value="v3.5"/></compiler></compilers></system.codedom>
Source File: E:\web\ultracvcom2\htdocs\dev\web.config Line: 68

 

Are you running orcas on Vista by any chance?If yes,see: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1301984&SiteID=1 .Also,try downloading the Orcas VPC image. The VPC image is based on Windows Server 2003, so you won't have any Vista problems.

Vikram

DiscountASP.NET
www.DiscountASP.NET

 

I found the real fix. I put back the original Web.config that wasn't working, saved it, and site stopped working as described in my first message.

I then right-clicked on the project in Orcas Solution Explorer, left-clicked on 'Property Pages'.

I changed the 'Build' - 'Target Framework' to '.NET Framework 2.0' from '.NET Framework 3.5'.

The site now works again.

 

FYI, '.NET Framework 3.0' also works.

 

Thank you all for your help, still having problems.


I am running WinXP Pro SP2, and have removed those two elements from <compilers> after backing up Web.config. I now receive the following error:


Line 60: <add verb="GET,HEAD" path="ScriptResource.axd" validate="false" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/></httpHandlers>
Line 61: <httpModules>
Line 62: <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/></httpModules></system.web>
Line 63:
Line 64:
Source File: E:\web\ultracvcom2\htdocs\dev\web.config Line: 62

 

Bruce gave me an idea, about backing up my Web.config file before I toy with it.

I found an old copy of Web.config on my harddrive, which looks totally different than the one created by Orcas, and used it. Everything seems to work fine now. I am pasting it here.

Is this ok to do? If so, then problem solved.







<!--


<configuration>


<appSettings/>


<connectionStrings/>


<system.web>


<compilation debug="false" strict="false" explicit="true" />


<pages>


<namespaces>


<clear />


<add namespace="System" />


<add namespace="System.Collections" />


<add namespace="System.Collections.Specialized" />


<add namespace="System.Configuration" />


<add namespace="System.Text" />


<add namespace="System.Text.RegularExpressions" />


<add namespace="System.Web" />


<add namespace="System.Web.Caching" />


<add namespace="System.Web.SessionState" />


<add namespace="System.Web.Security" />


<add namespace="System.Web.Profile" />


<add namespace="System.Web.UI" />


<add namespace="System.Web.UI.WebControls" />


<add namespace="System.Web.UI.WebControls.WebParts" />


<add namespace="System.Web.UI.HtmlControls" />


</namespaces>


</pages>


<authentication mode="Windows" />


-->


</system.web>


</configuration>