From Visual Studio 2010 Release Candidate back to Beta 2

If you’ve played around with Visual Studio 2010 Release Candidate (RC), you sure have noticed that it’s pretty fast. E.g. the WPF- and Silverlight-Designers come up quickly and much faster that in Visual Studio 2008.

But for now there are some reasons to wait before installing Visual Studio 2010 RC:

  • Silverlight 4 Beta is not supported. Silverlight 4 will be supported with the next public drop of Silverlight 4, what means when the Silverlight 4 RC is available. A date for that hasn’t been specified yet by Microsoft.
  • The available Preview Version for .NET 4.0 of Expression Blend doesn’t work with Visual Studio 2010 RC. It only works with Beta 2 of Visual Studio 2010. A new version will be available soon as the Expression Website says, but no one knows what “soon” means.

The second point I just noticed now. And so I decided to go back to Beta 2 cause I’ve a session about Model-View-ViewModel this week at BASTA! Spring in Darmstadt.

To go back to Beta 2, make sure you uninstall everything of the Release Candidate. After I’ve uninstalled Visual Studio 2010 RC, I had additionally to remove .NET Framework 4.0 from Programs in Control Panel. Tip: Order the installed programs by date, then you see what you’ve to uninstall pretty good.

After I’ve installed the Beta 2 again, everything worked fine. But I got an error when compiling my WPF-project telling me the following:

“GenerateResource” task failed unexpectedly. System.DllNotFoundException: Unable to load DLL ‘FileTracker.dll’ …”

After some search I found a connect-entry on microsoft.com with the solution. My folder “C:\Windows\Microsoft.NET\Framework” contained a “v4.0” directory additionally to the “v4.0.21006” directory installed with Visual Studio 2010 Beta 2. After deleting the additional folder that has a higher number than v4.0.21006 (it’s the RC ;-)), the Beta 2 works fine again and I can compile everything as expected. Find the connect-entry that pointed me to the solution here:  https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=501894&wa=wsignin1.0

Share this post

Comments (2)

  • Nikolai Manek Reply

    Hi there,

    just found a nice way of installing Silverlight 4 beta for Visual Studio 2010 RC.

    http://blog.andrew-veresov.com/post/Enable-Silverlight-4-Tools-in-Visual-Studio-2010-Release-Candidate.aspx

    March 13, 2010 at 9:05 am
  • Kevin Dahl Reply

    I get this error when I do an embedded resource in a static library.

    C:\WINDOWS\Microsoft.NET\Framework\v4.0.30128\Microsoft.Common.targets(1835,9): error MSB4018: The “GenerateResource” task failed unexpectedly.
    C:\WINDOWS\Microsoft.NET\Framework\v4.0.30128\Microsoft.Common.targets(1835,9): error MSB4018: System.DllNotFoundException: Unable to load DLL ‘FileTracker.dll’: A dynamic link library (DLL) initialization routine failed. (Exception from HRESULT: 0x8007045A)
    C:\WINDOWS\Microsoft.NET\Framework\v4.0.30128\Microsoft.Common.targets(1835,9): error MSB4018: at Microsoft.Build.Shared.NativeMethodsShared.InprocTracking.StartTrackingContextWithRoot(String intermediateDirectory, String taskName, String rootMarker)
    C:\WINDOWS\Microsoft.NET\Framework\v4.0.30128\Microsoft.Common.targets(1835,9): error MSB4018: at Microsoft.Build.Utilities.FileTracker.StartTrackingContextWithRoot(String intermediateDirectory, String taskName, String rootMarkerResponseFile)
    C:\WINDOWS\Microsoft.NET\Framework\v4.0.30128\Microsoft.Common.targets(1835,9): error MSB4018: at Microsoft.Build.Tasks.GenerateResource.Execute()
    C:\WINDOWS\Microsoft.NET\Framework\v4.0.30128\Microsoft.Common.targets(1835,9): error MSB4018: at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
    C:\WINDOWS\Microsoft.NET\Framework\v4.0.30128\Microsoft.Common.targets(1835,9): error MSB4018: at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask, Boolean& taskResult)
    ========== Build: 1 succeeded or up-to-date, 1 failed, 0 skipped ==========

    March 22, 2010 at 4:40 pm

Leave a Reply to Kevin Dahl Cancel reply

Your email address will not be published. Required fields are marked *

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.