Project Linker

Free

This tool helps to automatically create and maintain links from a source project to a target project to share code that is common to Silverlight and WPF. Therefore, shared code can be written once and built for the target environment.

(14) Review
Visual Studio
2010
Download (15,889)
7/1/2010
2.2.0.0
View
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (14)
Q and A (5)
Sign in to write a review
Sort by:

by ClipFlair | May 31 2013

for VS2012 see http://visualstudiogallery.msdn.microsoft.com/273dbf44-55a1-4ac6-a1f3-0b9741587b9a/edit?newSession=True

-----

BTW the "Prism guidance" link in the description is broken
instructions seem to be available at http://msdn.microsoft.com/en-us/library/ff921108(v=pandp.20).aspx

-----

WARNING: unfortunately the "Add project link..." dialog doesn't work correctly with Solution Navigator (installed by some Visual Studio 2010 add-on functionality pack), must use Solution Explorer instead (from VS2010 "View" menu)

-----

first time you link to a source project it doesn’t link all files from it, but after linking can move all files from that one to some temporary project and then back to the source project for the project linking extension to grab them and make links at the target project

-----

also note that the source project can contain links to files existing somewhere in the filesystem (use add link action at add existing item dialog), no need to include (copy) the files to it

by Sergio Parra | April 27 2013

great tool

by adventure_equation | October 31 2012

Great extension.

Please open source it so that the community can get it working with 2012.

by Miha Markic | October 05 2012

Genne's workaround works. Kudos. However, it is sad to see no official support whatsoever nor improvements

by Genne | October 02 2012

for VS 2012 Support
- rename it to .zip
- extract it
- open the extension.vsixmanifest file
- change <VisualStudio Version="10.0"> to <VisualStudio Version="11.0">
- zip the folder
- rename it to .vsix
--> install it

by perlun | September 26 2012

Agreeed. We MUST get this working with VS2012 again. I tried hacking the VSIX but it would lead to msbuild dysfunctioning at times (http://connect.microsoft.com/VisualStudio/feedback/details/760326/error-msb4014-the-build-stopped-unexpectedly-because-of-an-internal-failure-when-compiling-random-c-projects-with-vs2012). Uninstalling my "hacked" version of Project Linker made it work again, so it seems like it needs some work to function correctly with 2012 unfortunately...

by adam_uk_98 | September 26 2012

great - 2012 please!

by Sam Piper | September 19 2012

Pretty please release an official update for Visual Studio 2012, we REALLY need this extension!

by frindly | September 17 2012

+1 for 2012 support.

by Jason Worley | August 29 2012

Great extension, but I can't rate it any higher until Visual Studio 2012 support is added.

by Another Developer Guy | August 29 2012

This is so great, but it doesn't work in VS 2012 :(
Please get this working again .

by kayson | June 21 2012

Works like charm. However it does not allow you to chain the links, which is quite a limitation.
E.g. I have A,B and C. I want:
B contains everything in A.
C contains everything in B.

Right now the workaround is to have A==>B, A==>C, then manually sync between B and C.

by Radu Grama | January 25 2012

by NTDeveloper | Sat 3:08 PM

I LOVE this brilliant tool; so simple yet effective. Anyone who has tried to share source between projects knows what an absolute pain linked files are to manage. This tool completely solves the maintenance headache that using linked files introduces. Although the developers of the tool specifically highlight the use case of sharing common code between Silverlight and WPF applications, it is not limited to this specific scenario and can be used whenever you want to share code between projects. Moreover, this approach is considerably cleaner than the RIA services approach where shared files have to be named *.shared.* and the code is copied. Job well done!

Sign in to start a discussion


  • Visual Studio 2012 support
    4 Posts | Last post January 27, 2014
    • Probably can be hacked around to work with VS2012, but adding "official" support would be nice.
    • Yes, add VS2012 support and linking on demand (when referencing an non empty project). Wake up :-)
    • Please see the Projectlinker 2012 
      http://visualstudiogallery.msdn.microsoft.com/273dbf44-55a1-4ac6-a1f3-0b9741587b9a/edit?newSession=True
      
    • OK.....now I need the VS2013 version......
  • Crash with deep solution folder structures (100 % repro)
    2 Posts | Last post September 08, 2013
    • Every time I try to add a link to another project, I get a crash. My solution uses quite a lot of solution folders and it is when I try to expand a solution folder that I get the crash:
      
      The error message says: Assertion failed at Microsoft.Practices.ProjectLinker.VisualStudio.Helper.Design.SolutionPickerControl.CreateNode(TreeNodeCollection parentCollection, IHierarchyNode hierarchyNode)
      at
      Microsoft.Practices.ProjectLinker.VisualStudio.Helper.Design.SolutionPickerControl.OnBeforeExpand(Object sender, TreeViewCancelEventArgs e)
      at
      ...
      
      My solution folder structure looks like this:
      
      Solution
        * Solution Folder A
        * Solution Folder B
        * Solution Folder C
          * Solution Folder CA
          * Solution Folder CB
            * Solution Folder CBA
            * Solution Folder CBB
            * Solution Folder CBC
            * Solution Folder CBD
            * Solution Folder CBE
              * Project CBEA
              * Project CBEB
              * Project CBEC
              * Project CBED
              * Project CBEE
            * Solution Folder CBF
        * Solution Folder D
        * Solution Folder E
      
      There are some more projects and sub solution folders under the nonexpanded solution folders as well. The solution folder names and project names here are of course fake. Tell me if you need all the full names and structure and I'll send you the full solution.
      
      What I am doing when I get the crash is:
      Right click project CBEC and select "Add project link..." and then navigate by clicking the "+" icons. When I click the "+" icon for Solution Folder CBE, I get the crash and Visual Studio 2012 is nonrecoverable after that.
      
      The biggest problem is that I cannot use this extension at all, since the solution folder structure we are using is something that we want to keep.
      
      I hope that my explanation will make you find and fix the bug. :)
      
      I am starting to think that maybe this is not only a structure issue but also depends on which types of projects are in there. I have PCLs, iOS, Android, WPhone etc.
      
      /Ricky
    • Oh, it's recoverable by pressing Ignore. :-O
  • Visual Studio 11 support
    4 Posts | Last post September 19, 2012
    • The current version does not seem to support Visual Studio 11 Developer Preview. Is there any workaround for this, or a new version coming soon? I use this a lot. It just saves me a lot of time. Thanks.
    • This worked for me:
      1. Downloaded the vsix. 
      2. Extracted the contents with 7-Zip.
      3. Modified extension.vsixmanifest to add <VisualStudio Version="11.0"> to the <SupportedProducts> node.
      4. Changed MaxVersion to <SupportedFrameworkRuntimeEdition MinVersion="3.5" MaxVersion="4.5" />(not sure if this is necessary)
      5. Zipped up contents.
      6. Renamed extension back to vsix.
      7. Installed extension.
    • When I modify the VSIX file in this manner I get the following error:
      
       X The file is not a valid VSIX package
      
      Is there anything else that I can do to make this work in VS11?
    • Thanks for posting this, worked for me but not for all project types.  I use PL to cross compile between Silveright and WPF.  It works if I link the Silverlight project to the WPF version but not the other way around.  Throws a NullReferenceException somewhere in the extension.
  • Creating links to already existing files?
    4 Posts | Last post September 19, 2012
    • The tool seems to be creating links only for the files that are added to the source project after the projects have been linked.
      Is there any way to force it to create the links for all the files that already exist in the source project?
    • Indeed, I am wondering how did they miss that.
    • Try Caitlyn:
      http://visualstudiogallery.msdn.microsoft.com/079b3fca-e2b1-4fbc-8992-6b3f4134fea9/
    • I agree would be nice to be able to control this from the extension but there is a work around.  Simply exclude the files from the source project then include them again.  I find it easier to turn on the option to Show All Files first.  Then it is as easy as selecting the relevant files/folders using the Right Click menu to Exclude From Project then again to Include In Project.  As files/folders are included in the project the links are also created.
  • How do I use it?
    2 Posts | Last post November 23, 2010
    • A brief intro on how to use this tool would be nice.  I am not sure I even get what it really does, but an intro would help me understand that.
    • There in an intro here: http://msdn.microsoft.com/en-us/library/ff648745.aspx