VS2010: Project Linker - sharing single code base between Silverlight, WPF and WP7 applications

by 12. September 2010 12:25

This blog (and webcast) will show you how you can download, install and use the Project Linker within a few minutes.  Unfortunately it took me a few hours to figure it all out.

I had downloaded the source code for the Project Linker for Visual Studio 2010 from this link and was dismayed to see it was not going to be a plug and play.  The site only provided the source code and  this turned into a real head-banger because much was assumed on my part; I had no idea how to configure a VSIX definition so that I could deploy it.   I was going to be forced to learn more than I had time for but the return on investment was going to be there.  I had used the Project Linker for 2008 and it saved countless time in multi-targeted applications (within the context of WPF, WP7 and Silverlight).  

After spending (unneeded) time learning about VSIX files I stumbled upon a blog that noted that the Project Linker was available in the extension manager - I kept my fingers crossed and sure enough it was in there.   I was very glad to see it in there despite the fact I had spent numerous hours banging my head on the topic - hopefully you caught this blog early in the game ;)

The steps follow for Visual Studio 2010:

  1. Click on Tools
  2. Click on Extension Manager
  3. Click on "Online Gallery"
  4. Search for "Linker" (top right textbox)
  5. Click on the [download] button on "Project Linker"
  6. Click [Install] when prompted.
  7. System will restart VS2010
  8. Walla!  You have the project linker installed

The VS2008 Project Linker - sharing single code base between Silverlight and Desktop applications blog has the details (with Webcast) on the Project linker which hasn't really changed so the focus of this blog will be soley installation and use of the project linker.

Migrating Health Common User Interface from VS2008 to VS2010

by 11. November 2009 12:32

Initial efforts to convert/migrate the Microsoft Health Common User Interface from VS2008 to VS2010 failed miserably.   There were so many errors it wasn't real apparent where to start (after a few hours I gave up).  

After having converted a number of other programs I found there are a few consistent problems that once resolved move things along nicely.   They revolve around "Treat warnings as errors", Code Analysis and missing references.  If one of these occurs on an assembly that multiple projects have references to the error rate is compounded (making it harder to find).

After make the following few changes I found the Health Common User Interface compiles under VS2010:

Microsoft.Cui.SamplePages --- Add reference to System.Net

Microsoft.Cui.SampleWinForm --- Select None for "Treat warning as errors"

 

Uncheck "Enable Code Analysis on Build" for the following files:

  • Microsoft.Cui.ShowcaseControls
  • Microsoft.Cui.SamplePages
  • Microsoft.Cui.Roadmap
  • Microsoft.Cui.IsvDataProvider
  • Microsoft.Cui.Data
  • Microsoft.Cui.Controls

You'll want to remove the following three Unit Test

  • NhsCui.Toolkit.Test
  • NhsCui.Toolkit.Web.Test
  • NhsCui.Toolkit.WinForms.Test

If you don't you'll be prompted to convert the solution each time you load it as it will attempt to convert these and will fail.

Once the steps are complied with you can compile successfully!

VS2010, Silverlight 3 and Windows 7 - can't convert SL3 project

by 2. July 2009 00:39

My adventures started when I was notified that my Windows 7 beta was going to expire in 2 days.  While I continued to work on it I created a "production" development box; I've learned my lesson - don't install Beta on a production box...

With my production box functional I now had to create a Beta box which has all the cool stuff like VS2010, Silverlight 3, C# 4.0, etc.

The problem was with a fresh install you cannot convert Silverlight projects - I needed my PRISM projects (which I won't code without) and was dismayed to find out that everything "appeared" to work but the project never showed up.   The following is the fix! 

The following folder

C:\Program Files (x86)\MSBuild\Microsoft\Silverlight

Only has a v3.0 folder. I copy/pasted this folder and renamed the copy to v2.0 and the project would successfully appear after conversion.

 

 

VS2010 - The ServicePointManager does not support proxies with the https scheme

by 18. June 2009 06:16

I created a Codeplex project for a Visual Studio 2010 solution and was greated with the error "The ServicePointManager does not support proxies with the https scheme".

When you Google for "VS2010 Codeplex" you will find the following link at the top of the list:

http://coolthingoftheday.blogspot.com/2009/05/have-vs2010-beta-1-trying-to-connect-to.html

Where I was very happy to find a solution I was disappointed that it was only partial; it didn't provide the actual registry entries.  I found a blog that actually provided the registry settings and was disappointed when it didn't work.  

So I continued my search and was glad to find the following blog because it actually provided the commands necessary to automatically add the required registry entry.   It seemed to match what I did manually so I trust I made a typo somewhere.

The following link fixes it:

http://blogs.msdn.com/ablock/archive/2009/05/20/for-tfs-2010-beta-1-resolving-tf31001-the-servicepointmanager-does-not-support-proxies-with-the-https-scheme.aspx

I deleted my entries and ran the above commands for a 64bit environment and "walla!" I was able to connect to my codeplex project using VS2010!

For you 64bit folks the following batch file may save you a few steps

tfsFix.bat (267.00 bytes)

Note: In case their site is down at the time you need it I provide an excerpt (important stuff) from the above link:

If you are receiving the TF31001 error, you should be able to resolve this issue by running the following commands:

On all machine:

reg add hklm\SOFTWARE\Microsoft\VisualStudio\10.0\TeamFoundation\RequestSettings /v BypassProxyOnLocal /t REG_SZ /d False

reg add hklm\SOFTWARE\Microsoft\TeamFoundationServer\10.0\RequestSettings /v BypassProxyOnLocal /t REG_SZ /d False

 

Additionally on a 64-bit machine:
reg add hklm\SOFTWARE\Wow6432Node\Microsoft\TeamFoundationServer\10.0\RequestSettings /v BypassProxyOnLocal /t REG_SZ /d False
reg add hklm\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\TeamFoundation\RequestSettings /v BypassProxyOnLocal /t REG_SZ /d False
  --Aaron

 

Notice

Blog videos and references to CodePlex projects are no longer valid