I recently switched from using a Mac to using Windows to build a .Maui app. Prior to the switch, I was able to create a new project and select a "shared project" project type to create code to be shared across multiple projects. I'm trying to do the same thing now in Visual Studio 2022 Preview Version 17.5 Build 437 and can't find a "shared project" option when creating a new project.
Can anyone point me in the right direction? If this option isn't available, do you have suggested workarounds?
I tried reinstalling VS and looking for options to install additional templates. I also looked for an extension that might add this option. After much research, I still don't have an answer.
I was working fine with in my project ,the once I updated my Xamrain.Forms to 3.0, all of a sudden I got this error :
Has anyone come across this issue? I'm kinda lost here, thanks .
Issue with my project was that, Project.Android and Project.iOS's Nu Get packages Xamarin.Forms's versions were different, so I had to update all Xamarin.Forms library in each project to the same version.
Clean, Build and it solved the issue.
Please ensure that all projects reference the same version of
Xamarin.Forms
So make sure that the statement above is correct, clean your solution and just in case restart the Visual Studio after that.
EDIT:
It seems to be a quite popular issue after upgrading to Xamarin Forms 3.0, if the steps above didn't resolve it please consider:
Delete all /bin, /obj and /packages folders within the solution
Check csproj files for duplicated Xamarin Forms references
Re-add Xamarin Forms NuGet packages
this should help:
You need to click RMB on each (Droid, IOS, UWP)-project -> Nuget -> and then update Xamarin Forms for every project to the same version, even "solution".
I would not call it a solution, but uninstalling the app from the device prior to every build was the only way forward I have found.
I tried all of the above to no avail.
What helped me was the following:
Close Visual Studio (for mac in my case)
nuget locals all -list
Delete all nuget cache folders
Restart visual studio and try again.
I am using the AppBuilder to create a NativeScript app. I am at the point that I need to start looking into environment settings to get the app ready for QA and production.
I followed the article: http://docs.telerik.com/platform/appbuilder/nativescript/build-configurations/application-settings in order to set the config.js file I have that contains some configuration information. I created config.debug.js and config.release.js but Visual Studio only added the debug version under the config.js file group.
So, when I build in Debug mode, the app picks up config.debug.js and everything is fine. When I try to build in release mode, the app crashes because it cannot find config.js. Attached is a screenshot that shows how Visual Studio sets the files.
It seems to me that since the release version is not included in the file group nativescript does not recognize it during the build.
I am using Visual Studio 2015 Enterprise. App Builder 2017.1.202.9
Any suggestions will be highly appreciated.
Thank you.
As suggested by Preslav from Telerik, I deleted the .debug.abproject from the root of my application and also removed the reference to it in MyProject.iceproj.
Once this was done, I was able to create the .debug.js and .release.js files without any further issues.
I am running Visual Studio 2012 plus Xamarin.iOS with the latest version of each. I have Portable Class Libraries in which I want to select the latest "Xamarin.iOS" release as a build target (instead of MonoTouch). In Visual Studio I open up the Project's Properties, select the Library tab, and click on Change under Target Frameworks. However, I am unable to modify any of the checkboxes. Any checkbox I change instantly closes the "Change Target Frameworks" dialog. If I change one of the dropdowns (for example, change from .NET 4.0+ to 4.5) then when I go to click OK the changes do not get reflected in the Target Frameworks list.
Anyone have any idea how to resolve this issue?
I was able to resolve this by changing the TargetFrameworkProfile in the XML of the csproj file. I was on Profile104 which is no longer supported, so I manually removed this and left this blank in the XML, and then was able to re-add the profile targets (after using the dialog it put me on Profile136).
I've encountered a similar problem , while trying to add MvvmCross Nuget Package. I've to change PCL profile to 259 , it didn't allow me ( Xamarin Studio on iOS) , Ok and Cancel buttons are not present.
I opened the .csproj file in TextEditor.
Removed the PCL profile information. Reopened the project.It gave me build error.
So added following string manually
Profile259
It Started working.Hope this information helps.
I'm opening a solution that was apparently built on Visual Studio 2003 (not sure, I don't know anything about it) and trying to migrate to 2010. When trying to migrate I get the message:
the application for project '' is not installed make sure the application for the project type (.csproj) is installed.
If I open each one of the single projects of the solution they migrate fine but not the solution itself.
Right-click on the project file, then "Reload"
If your solution opens, but your project is showing as "incompatible", it may need to just reload. This worked for me when running an update from VS, and it did not recognize my njsproj
I know this is an old question, but it is still occurring in VS 2013.
I had an old VS 2003 web application. I opened it in VS 2013 (Ultimate) and had the error message:
Could not find the server on the local machine.
Creating a virtual directory is only supported on the local IIS server
along with
The application for project is not installed.
Yes, I am upgrading, and yes, I don't have some other elements ready. Giving me errors is fine - but why are you not completing the migration/load of the project. I can't fix the other issues if you don't LOAD ANYTHING! You loaded the subprojects, and then you told me that I should choose a later .NET Framework. Great, I did that. So why didn't you just finish loading the main project and let me fix the errors?
Lots of attempts to fix this failed. My final solution, just to get the project loaded was {arrow pierces chest, dies with Arghhhhhh on his lips}...
I located the {project}.csproj file. I found the <Reference> sections. The paths to the .NET Framework components were no longer valid and referred to old versions no longer installed (yeah, upgrading, remember?). I manually changed the paths to refer to .NET Framework 4.5 components. The project still didn't load.
Then I located the {project}.csproj.webinfo file. It referred to http://localhost/{stuff}/{project}.csproj, so I just set it to {project}.csproj. No luck. Then I just renamed the webinfo file to hide it. Eureka, the project was hot!
The project loaded, I got the "You have completed the first step in converting your Visual Studio .NET 2003 web project. To complete the conversion, please select your project in the Solution Explorer and choose the 'Convert to Web Application' context menu item." Which, of course, is not present, but is present as the very last item in the Project menu. Then I got the "This action will add designer and code behind files required for converting Web site projects to Web application projects. Do you want to continue?" You bet your posterior I want to continue! And now I have a project I can actually start to fix. Thanks, Microsoft, for the informative error messages.
If your projects individually migrate fine, then create a new blank visual studio 2010 solution, and add new projects individually (right click on solution->add->existing project)
But I'm not sure that your projects will load fine individually. There are project types that require some additional software to be installed in order to be supported. The most frequent problems I face are old projects built with old versions of asp.net mvc (1 or 2) and I have asp.net mvc 3 installed...or really old projects built with asp.net ajax...In those cases, you have to install that additional software and then import project, or find a tool to upgrade that project type to a newer version.
I found a solution that worked for Visual Studio 2017.
In Visual Studio, go to Tools > Extensions and updates. At the upper-right search box, search for "integration". It should come up with Analysis or Diagnostic Tools (or similar). Click Disable, then Enable. Exit the dialog, and close Visual Studio. Relaunch and open your solution again. Your projects will still complain they can't be loaded because of incompatibilities, but now you can right-click them individually and select "Reload Project" and they should load fine.
Credit goes to Paul Potter and Paul Shaughnessy at https://developercommunity.visualstudio.com/content/problem/216061/project-incompatible-application-not-installed.html - I just did the verification work, condensing the information, and delivery :)
Adding this answer as reference for people who landed here for missing ".smproj" file.
This issue can arise due to various project files missing. For me, it was because of ".smproj" file missing which is Project file for SQL Server Analysis Services(SSAS). I re-installed SQL Server Data Tools (SSDT) and restarted the Visual studio.
Originally Answered here
Sometimes the SSIS or SSAS Extension in "Manage Extension" is disabled in the settings and must be Enabled manually. And then restart Visual Studio
It happened to me as wel.
You usualy do really need only to reload project in the solution. But in some cases you maybe:
didn't install SQL Server Data Tools (SSDT) for VS
have to enable SQL Server Data Tools manualy in the Extensions
If you have both things settled then try to reload project again. This happened to me when I moved from VS2019 to VS2022 and extension was somehow disabled.
I am using visual studio 2019 and I was faced with this issue when I reopened my ASP.Net webform App in visual studio after modifying for install SSDT.
this problem happens when Visual studio packages will modify (Especially when SSDT will be installed).
To solve this problem you have to go to you project folder and looking for the folder that named '.vs', this folder is hidden.
Deleting these folder will solve the problem because after that when you will open your project with visual studio, it will create the folder again.
Adding this for those who face issues for SSRS projects in VS2017 from earlier version as this comes up in google search.
In Visual Studio, go to Tools > Extensions and updates. Download the below :
Microsoft Reporting Services Projects
Microsoft RDLC Report Designer
In SSIS 2017, t the upper-right search box, search Microsoft Integration Services Projects.
go to Tools > Extensions and updates.
Enable -"Microsoft Integration Services Projects"
This will help to resolve the issue re-launch the SSIS
For my case, I disabled this extension and turns out, it is needed.
Enabling it resolved my problem.
In VS2019 Before you try any of the above right click the solution and click "Resolve Errors" no kidding that made my tabular model solution being available again.
For me what worked was a variation of #vapcguy solution.
Go to #vapcguy link for Paul Potter and Paul Shaughnessy solution: https://developercommunity.visualstudio.com/content/problem/216061/project-incompatible-application-not-installed.html - I
Follow comment on Paul Potter's post by Albert Romeo
Integration Services Plugin was disabled(as explained before: Goto Tools > Extensions and updates > and search for integration/analysis/reporting and enable application
I had to enable integration services, then reload project. I don't know why since I've been using the same SSIS project several times a week for months.