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.
I have this entry in my SharedProject.projitems file
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 :)
This extension seems really useful, is there any reason for which it's only applicable to the Pro version of Visual Studio? Can I modify it to install it on my VS 2013 update 3 Express for Windows Apps?
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)
Created a project using Universal Apps > Hub App (Universal Apps) template in my preexisting solution. I have some portable class libraries in the same solution that I would like to use in the .Shared project's SampleDataSource.cs
But there is no References branch in this project. Other two projects - Windows 8.1 and Windows Phone 8.1 have the References branch. Please help!
HI. Keen to try this out but unable to insall, install log shows:
5/09/2014 2:19:06 p.m. - Found installed product - Microsoft Visual Studio Express 2013 for Windows Desktop
5/09/2014 2:19:06 p.m. - Found installed product - Global Location
5/09/2014 2:19:06 p.m. - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
any tips most appreciated.
Uninstalling this addon fixes this issue, reinstalling it brings it back...
I have a solution with 20 C++ projects in it.
When this addon is installed and all projects are loaded the Build Solution, Rebuild Solution and Clean Solution buttons are disabled.
With 12 projects loaded it's the same.
With only 11 projects loaded (any 11) the Build Solution and Rebuild Solution buttons are disabled.
With 10 Projects the Build Solution button is disabled.
9 or less solutions then all buttons are available.
I installed VS Update 3 recently, and haven't seen this problem with Update 2. Could this be a thing?? It's driving me insane :)
I am trying to add this extension to visual studio 2013 premium. I have tried multiple times with restarting visual studio, but i still get same following error.
"The 'SAPReferenceManagerPackage' package did not load correctly."
Any help for solving this issue is greatly appreciated.
first of all, thank you very much for this extension. Shared projects make my life so much easier. For now I just use them with universal apps. With this extension I had hoped to use it in the largest of my apps to make some things a lot easier than I currently do with PCLs.
However, I'm running into a lot of issues. Mainly Visual Studio freezes and compiler issues.
I can see that the last update on this happened on April 18th. Any chance for an update here soon?
I'd also be willing to send you my whole code so that you can have a look. For now, I don't want to try out VS 14 CTP as it is not recommended for production plus I think that WP is not supported 100% yet.