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.
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
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...
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.
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!
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.
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?
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.
View Large
