Shared Project Reference Manager


Manages References to Shared Projects

(20) Review
Visual Studio
Download (18,495)
E-mail Twitter Digg Facebook
Add to favorites
Reviews (20)
Q and A (24)
Sign in to write a review
Sort by:

by 광박 | June 10 2015


by LaurentDuveau | May 15 2015

by Damian Suess | March 28 2015

Seriously, great job!! I love using this with my Xamarin projects and also Windows Desktop solutions in Visual Studio.

You easily solved tons of man-hours and we no longer have to duplicate code across or build another DLL to house all of these items. Its so nice having everything all together when need be!


by WhiteBahamut | March 18 2015

Awsome! What I was looking for. Was messing around with my shared project and had a few problems re-adding it. This extension did the magic.

Well done!

by George I. Birbilis | March 18 2015

hope to see this as standard VS functionality, after all Xamarin Studio has such from what I know

1) After installing you have to restart VS2013 to see the template I think
2) the template icon shows a mobile phone, could show instead the same icon (with a language icon overlay, like C#) as the one shown inside the Solution Explorer pane (two overlapping rhombi)

by Nikola Prokopić | March 13 2015

One word - Magnificent!

by Mike-EEE | March 10 2015

Works perfectly! Why this is not default functionality is beyond me.

by kczx | November 16 2014

I love this concept and it would really be great to see this working with MVC

by Sam Karim | September 03 2014

by ramani_ankit | August 13 2014

by arens | August 11 2014

I totally love shared proejcts. It makes live so much easier. Unfortunately, I'm running into a lot of issues for the current version which I didn't encounter for universal apps.

by Javier Canton Ferrero | July 15 2014

Great new feature!

Will it come by default in Visual Studio 14?

The only problem for us is that we use different embedded resource on each platform for the same library. Waiting for something to handle this XD.

by Michael Dour | June 25 2014

This tool is great and really helps manage the complexity of projects that need to share the same source so you don't need to use linked files.

There is one issue with it though: when a project file is checked in to source control, trying to add a shared project reference to it crashes VS.

by Rehan Saeed | May 14 2014

Good but the ability to reference a shared project from another shared project would be nice.

by kam003 | May 13 2014

by Todd-Vertigo | May 13 2014

As most architects know, this has been possible for a few years by manually baking your own MSBuild files. The heavy cost with this technique is keeping teams inline with the churn; often updating the builds gets missed.

Thanks for pulling this close to the VS experience. This makes a huge difference to many project roles.

by Oren Novotny | April 18 2014

by Andrew L Arnott | April 18 2014

Very cool. Now using it for the PCLCrypto library.

by Tim Heuer | April 18 2014

Great to see this!

by navits - MSFT | April 18 2014

Sign in to start a discussion

  • Vs2015 Please!
    2 Posts | Last post July 29, 2016
    • We need this in visual studio 2015 because you cannot add shared projects to web applications.  The "Shared Projects" tab in the referrence manager does not show up in Web Project Types.
      However I know it works because I can manually add them in the project file and it works fine.
    • How did you manually add it to a web application project, because it doesn't work if I do it manually.
      I added it like:
      <Import Project="..\{path-to}\{project}.projitems" Label="Shared"/>
      It shows up, but when I build I get the error:
      CSC : error CS2001: Source file 'D:\{Path-to-File}\ReverseGeocodeInformation.cs' could not be found.
      It looks for the file in the website directory, not in the SharedProject directory.
  • Adding resources
    1 Posts | Last post February 22, 2016
    • I can't seem to get resources to work.  They don't end up in the output assembly.  When running, I get this error:
      "Could not find any resources appropriate for the specified culture or the neutral culture.  Make sure "Foo.MyControl.resources" was correctly embedded or linked into assembly "Foo" at compile time, or that all the satellite assemblies required are loadable and fully signed."
      The same solution builds and works fine in Visual Studio 2015.
      The resx file in the shared project is marked as Build Action=Embedded resource, Copy to output directory=do not copy, Custom Tool=[blank], Custom Tool Namespace=[blank]
      The Default Namespace in the shared project is 'Foo' (not that I think that matters as it did in non-shared projects).
      Anyone got any ideas?
  • No VB.Net Support?
    1 Posts | Last post August 17, 2015
    • Sharedprojects in VS2015 support VB.Net, but this Extendion in VS2013 only supports C#/VC++/VJS ?
      Is there any plan to add VB.Net support, or do we have to use VS2015 on all machines in order to use shared projects with
  • Would this work on VS 2015?
    1 Posts | Last post July 22, 2015
    • I'm sure there would be some changes, but it would be nice if this would work on vs2015.  The shared projects in vs2015 require the wp8.1 sdks which won't install on Windows 7.
  • No way to cancel adding a shared project reference
    1 Posts | Last post July 20, 2015
    • I just noticed the following issues:
      1. In the SPRM dialog, once I checked a shared project, I can't uncheck it. If I click the checkbox again, it adds the reference again, so if I click the checkbox N times, I end up with N <Import> nodes in my .csproj (although only one appears in the References node in the Solution Explorer)
      2. There is no Cancel button in the SPRM dialog; so if I checked a shared project by mistake, I can't uncheck it (due to issue 1), and I can't cancel. Closing the dialog does the same as clicking OK: the references are added anyway.
  • Performance issue with large solutions
    2 Posts | Last post June 24, 2015
    • Performance profiling shows that with a large solution (384 projects, sadly), this plugin will spend a long time updating UI controls with the list of available projects when closing the solution. Closing this solution takes 2 minutes, 90 seconds of which is the plugin updating the UI. Actually, it's Visual Studio being really slow at marshalling with the command bars, but it's still crazy slow. I believe the plugin also has an impact on loading the solution, for the same reasons, but I haven't measured.
    • I also have large perf issues, when opening ConfigurationManager and changing the platform and switch between debug/release. In the stack I see SAPReferenceManager.dll!Microsoft.VisualStudio.CommonIDE.LoadedProjectList::OnAfterInvalidateHierarchyItem takes a lot of CPU time. I disabled the Extension ,because I don't really do store app coding, this extension was only installed for testing purpose. The Extension should be only activated for Store App Projects and no other ones.
  • Primary benefit(s) of Shared Projects?
    2 Posts | Last post June 05, 2015
    • So - when would I use a Shared Project? 
      - for instance, if one created some libraries / components shared among solutions, would you use a Shared Project then and IF that's the case, how does TFS handle shared projects as sharing sources within TFS is not an easy task.
      - or is Sharing Projects mainly used for sharing code among various architectures? (as in almost every sentence, which mentions Shared Projects is also mentions Windows Phone)
    • The reason that Windows Phone is mentioned is that the original purpose of a Shared Project was to provide a single place to write common code that would be used in both versions of a Universal App.  The code that was phone-specific would go in the phone project, the code that was PC specific would go in the PC project and the common code would go in the shared project.
      Like various things, people have discovered that shared projects can be useful for more than what they were originally intended, so the scope has been expanded.  Currently, in my office, we are creating a second MVC application that is based on an existing application but with a few changes.  We are using a shared project for controllers that are the same or similar in both applications.
      The difference between using a shared project and a common class library is that the code in the shared project is actually compiled into the other projects that reference it.  As a result, it's actually possible to declare partial classes with one part in the shared project and other parts in the project(s) that reference it.  In that way, we're able to use a shared project for controllers that are similar but not the same.  All the common code goes in a partial class in the shared project and then application-specific code goes in another partial class in the appropriate application project.
      With regards to MVC, it appears that a shared project doesn;t support views at the moment.  Presumably that will be addressed at some point but, for now, the Razor Generator extension and NuGet package can be used to put them in a common class library.
  • Intellisense not working
    1 Posts | Last post March 28, 2015
    • While working on my solution, the classes under the Shared Project lost the use of Intellisense. Is this something that is common or a known issue?  Keep in mind this solution is very small and only consists of a few classes & isn't monstrous just yet.
      Most notably its happening on my SqlDataAdapter and SqlConnection. At first i just needed to recompile the whole solution and then it came back. Now it's not working at all for any class in the Shared project space.
      Any thoughts?
  • Support Visual Studio 2015
    2 Posts | Last post March 25, 2015
    • Is it possible to add support for Visual Studio 2015? I am hooked to this extension but must upgrade to support the new Windows 10 stuff.
    • Never mind, it's integrated into VS 2015, even better :-)
  • Path is ignored for Page project items
    2 Posts | Last post March 04, 2015
    • I have this entry in my SharedProject.projitems file
        <Page Include="$(MSBuildThisFileDirectory)Styles\Dictionary1.xaml">
      When built it appears in the .dll'r resources as:
      <data name="dictionary2.xaml" type="System.Resources.ResXFileRef, System.Windows.Forms">
      As you can see "Styles\" path is lost and if I reference this resource dictionary in App.xaml like this:
      <ResourceDictionary Source="Styles\Dictionary1.xaml" />
      it cannot be resolved and crashes. However referencing resource dictionary like this works:
      <ResourceDictionary Source="Dictionary1.xaml" />
      I feel it is a pretty easy bug, if only this project was open sourced... I'd fix it straight away :)
    • NOTE: this is only relevant for WP8 Silverlight apps (Store apps are ok)
1 - 10 of 24 Items