Microsoft hat gestern das Service Pack 1 für Visual Studio.NET 2003 released.

Die Release Notes finden sich hier.

Im DDCPX Team Blog wurde das Service Pack 1 Beta für Visual Studio .NET 2003 veröffentlicht. Download für Interessierte ist unter http://connect.microsoft.com möglich.

Erhält man bei Kompilieren einer Applikation in Visual Studio 2005 eine Fehlermeldung wie diese:

"Compiler Error Message: CS0006: Metadata file C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\spsweb\0e3514bf\cb1844e7\assembly\dl2\3b163f16\00452d31_84e5c301\infragistics.webui.ultrawebgrid.v3.dll (Name ist beliebig gewählt) could not be found"

sollte man u.a. sich auf der Suche nach Diensten wie dem Indexdienst machen. Dieser sperrt nämlich solcherlei Dateien nämlich gerne - das Resultat hatte ich bereits Eingangs gepostet ;-)

In meinem Fall war es übrigens der "Microsoft Search" Dienst - Beschreibung:

"Creates full-text indexes on content and properties of structured and semi-structured data to allow fast linguistic searches on this data"

Vermutlich installiert bei der Installation der Windows Live Toolbar - noch nichtmal eine Stunde installiert und schon gibts den ersten Ärger...

S. 'Soma' Somasegar (VP, Developer Division) has announced the Visual Studio and .NET Framework Servicing site on MSDN.

The site includes new information about the Visual Studio and .NET Framework servicing roadmap and the Microsoft servicing process.  It also aggregates a large amount of information about released software updates that was previously difficult to find.

You're not happy with the ways you're able to deploy the runtimes of the software you're developing (using Visual Studio.NET)?

Tell Microsoft what they can do better.

If you want to limit your code lines in VisualStudio.NET 2003 or 2005 Beta 2 to let's say a length of 80 chars, there's a little help by "hacking" your registry:

You can activate a colored vertical line in the VisualStudio.NET editor that tells you where char number 80 is.

Touch your registry at your own risk! Back it up before modifying it!
 
Start RegEdit and open the following key:
 
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\7.1\Text Editor
 
Create a new string named "Guides" and assign the value "RGB(128,0,0) 80".
 
This will display a vertical rule after 80 characters.

It's also possible to create more than one rule, for example "RGB(128,0,0) 80, 95".

Imho it is the easiest way to debug ASP.NET 1.1 applications as non-admin using VisualStudio.NET 2003, when you're following these instructions:

Grant the following rights to your LUA (= Limited User account) for the directories listed below:

&INSTALLROOT% is of the form c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322 and %WINDIR% is of the form C:\WINDOWS.

After this you have to add your LUA to the security groups 'Debugger Users' and 'VS Developers'

By default, with a restricted user login, you cannot debug Web applications because the user running the debugger is not a member of the proper group to debug other users' programs (Administrators), and the Web server started ASP.NET as the NETWORK_SERVICE account.

If you do not want to grant this login membership in the local Administrators group or run the debugger as the local Administrator, you need to change the account that ASP.NET is running as. On Windows XP Professional, edit machine.config as shown below and put in your username and password in clear text. This has the potential disadvantage of requiring all ASP.NET applications on the machine to run as your user account, but is the best method for IIS 5, and allows you to debug and build Web apps the same way you did in the past.

As an Administrator, edit the attributes of the file "%INSTALLROOT%\Config\machine.config" 'on the processModel tag, as shown:

<processModel
                enable="true"
                userName="DOMAIN\username"
                password="MyPassword"
                ...
/ >

If you do not set a restrictive ACL on the machine.config file, putting your userid and password in cleartext allows anyone to see your password. Even if you set a restrictive ACL, all users in the Administrators group will still be able to see it.

The resolution to the above security risk is the following: Use the aspnet_setreg.exe utility to put an encrypted version of the LUA's username and password in the registry by using the following command:

aspnet_setreg.exe -k:SOFTWARE\MY_SECURE_APP\processModel -u:"username" -p:"MyPassword"

Then modify the processModel as follows to point it to the registry:

<processModel
    userName="registry:HKLM\SOFTWARE\MY_SECURE_APP\processModel\ASPNET_SETREG,userName"
    password="registry:HKLM\SOFTWARE\MY_SECURE_APP\processModel\ASPNET_SETREG,password"
...... />

By default the DACL on the "HKLM\SOFTWARE\MY_SECURE_APP" hive grants Full Control to only System, Administrators and Creator Owner. Since ASP.NET is running under my userid, the caveat here is to make sure that I gave my userid (ex. "username") Read access to this registry hive where the userid and password are now stored.

My machine needed to be rebooted after modifying all these settings - so it won't by a disprofit if you do it also ;-)

Just read about the minimum system requirements for the VSTS VPC Image available at MSDN Subscribers Download at Rob Caron's Blog - seem's I have to buy a new notebook...or just use the tools Chris introduced at his TechTalk.

Btw: The slides, demos and links from Chris' TechTalk can be downloaded here.

Seit einigen Tagen ist der Visual Studio 2005 Express Edition Beta 2 Help Fix zum Download verfügbar. Er behebt Probleme mit der Integration .NET Framework API Dokumentation in Visual Studio 2005 Express Edition Beta 2.