I have a windows phone application build for windows phone 8, in Visual Studio 2012. I have started incorporating azure, and found that Visual Studio 2013, was a smarter choice for this. Therefore I installed the new VS, and opened the file, but I cannot get it to upgrade the solution.
I use the Visual Studio Version Selector as default opener, and it open the solution in my VS2013. But it is still VS2012 version, as can be seen on the picture:
I have tried to use Save as, which is stated as a solution here. But still the solution does not change. Anyone has a suggestion for how to upgrade the solution to VS2013?
What I want to use is what is shown in this video on Channel9. So I need to some how upgrade my project, or do I have to copy the code to a new project :-/ ?
I tried installing the SDK's from Microsoft Azure, but still no luck.
EDIT
The feature where you add connected service is not available for windows phone. And you do therefore not need to upgrade the VS solution. But still I had problems getting access to the server.
Go to "View", and click "Server Explorer". There one can see a windows/Azure logo, by clicking it you will add your windows azure account. apparently this does not mean adding your services even though it states that you are logged in and with the correct subscription.
Solution
However the solution I stumbled upon was to add a new Mobile Service. Where then get prompted to choose my subscription which then was not there. Apparently the subscriptions can be loaded in different ways. Therefore in this new popup under subscriptions choose import. And you basically get the route described.
After importing the subscription, you then cancel creating a new services(If you did not need it :)). And now all your azure stuff will be accessible to manage as seen in this link.
However it does not create the code lines since you are not using "add connected services" which is possible in windows apps.
Finally an answer :)
You cannot convert solution from Visual Studio 2012 to 2013 because it is not changed at all.
Sln is just xml file and it is remain same so there is no need to convert it from 2012 to 2013
Related
After Installing Visual Studio Community 2022 version 17.3.4 I have tried to create new new project on asp .net web application(.NET Framework)(c#), but it is not working as you can see it constantly saying object reference not set to an instance of an object. I have tried to run it as administrator. I have done most of the things I have found on the internet but nothing seems to work.
Hum, I am running 17.3.4, and it works just fine.
I would consider doing a repair - see if that helps.
tools->get tools and features.
You get this:
(it actually opens two pages). So close the above form, and then you get this:
So, try the repair.
I suppose ensuring that previous (legacy) templates are also installed would help, but first try a repair.
Edit: Installing legacy templates
Ok, in comments it was asked what additional install(s) is one to select.
From VS menu tools->get tools and features.
You get/see this:
In above, expand the "ASP.NET and web development" on the right
this:
And then select these:
(can't remember which exactly from above gets you everything, but given doing legacy development, good idea to select all that I pointed out).
I'd like to install the Xamarin Studio on Windows so I searched on google and it led me here https://store.xamarin.com/account/my/subscription/downloads. I clicked the download and the setup begins. I clicked CONTINUE and 'yes' to allow changes to my computer. And after that, nothing happened. I waited for a few minutes and still, nothing happens. I went back to that link and repeated all the steps but again, it didn't work. Help me pls I really need the XS :(
#Kristine
The best way to have Xamarin is installing the VS, since the 2015 version you can have Xamarin inside VS. BTW, you don't need to pay (but you can if you want to) because there is Community version of VS.
On Windows OS, you don't need to download Xamarin Studio for developing with Xamarin.
Use VS 2017 is better, you browse https://www.visualstudio.com/vs/community/ to download and install Visual Studio 2017 because it supports Xamarin now(https://blog.xamarin.com/better-apps-visual-studio-2017/)
After you started downloaded file, you will see some options that you can choose. You can choose Xamarin.
If you don't know which ones should be chosen, just choose all.
It works for me.
I'm facing an annoying problem involving my installation of Visual Studio 2015 Enterprise. I just got into a cross platform mobile project and I have fetched the source code from version control. The solution consists of several mobile projects (Android, iOS) that work fine and a UWP project that refuses to load. It says on the solution explorer:
This project requires a Visual Studio update to load. Right click on the project and choose "Download Update"
After clicking "Download Update" I'm presented with this page: https://developer.microsoft.com/en-us/windows/downloads/sdk-archive .
I've tried downloading all three of the SDKs (I don't think it's an emulator issue so I haven't bothered download the emulator installers).
All three throw this error:
I've tried modifying my Visual Studio installation from the control panel but as you can see the installer claims all Windows SDKs are currently installed:
I've tried re-installing the SDKs. I've tried reinstalling Visual Studio 2 times, one of them involved a full uninstall by running
vs_enterprise.exe /uninstall /force
in a command prompt but to no avail.
Also when I try to create a fresh UWP Project the only platform I can target is the 10.0.240 build. I recall being able to target other versions in the past but the dropdown only contains this option now.
I finally solved it after quite a lot of research. I followed these steps:
Go to Control Panel > Programs & Features
Find Microsoft Visual Studio 2015, right click on it and select 'Change'
When the installer pops up select 'Modify'
Uncheck the whole 'Universal Windows Apps Development tools' section
Wait until the uninstallation is complete
Restart
Again go to Control Panel and find the SDK installers which apparently are not removed using the above method:
Uninstall them all
Restart
Visit this page: https://developer.microsoft.com/en-us/windows/downloads/sdk-archive and download all three SDKs
Start by installing version 10.0.26624 and work your way up
After you're done go to control panel find the Visual Studio Installation, right click, click 'Change' then after the wizard loads select 'Modify'
Make sure every option in the 'Universal Windows Apps Development Tools' section is checked, click Next
After the installation of the SDKs and tools is complete restart your computer
The error should be gone now
I ran into this error trying to add a Portable Class Library project to a solution. It occurred whether I asked it to target Windows Universal 10.0 or Windows 8.1.
The workaround I used is to ask it to also target ASP.NET Core 1.0, even though I wasn't using ASP.NET.
I also ran into this which took me a lot of time to solve. Actually YOU DON'T HAVE TO REINSTALL ANYTHING! If you are totally sure your Visual Studio is up to date, just follow these steps and it will solve your problems: https://stackoverflow.com/a/35733823/3322347
I'm trying to use an in-house custom tool that generates C# code from XML in Visual Studio.
The last time I successfully used the tool was about a month ago, since then I've updated from Windows 8.1 to Windows 10 and have also updated Visual Studio 2015 from Update 2 to Update 3. I have colleagues who were using Windows 10 and Update 3 before they installed the tool for the first time and there are no problems finding the tool for them.
There have been no changes to the tool made since updating Windows and Visual Studio.
When I tried to use it today I'm seeing the error
"Cannot find custom tool on this system".
I've tried uninstalling and reinstalling my tool, as well as calling devenv /setup, as well as deleting and readding the extension gallery for my custom tool. I've also tried repairing Visual Studio, to no avail.
I've checked the registry and I can see the key for the tool there.
Has anyone else experienced the same issue, or got any suggestions for other things I can try?
Thanks a lot!
The reason why the custom tool couldn't be found is because the strong name wasn't being verified.
I fixed the issue by running sn -Vr *,(missing public key) to add the assembly to the verification skipping list.
I don't know why the custom tool could be found prior to the Windows 10/Visual Studio upgrade. My best guess is that the verification list previously contained it and was lost whilst upgrading to Windows 10.
I am using VS 2013 (Express Version) and I want to create a WPF user Control Library project. But I am not able to find the template in my installed templates list. If I use Winforms, I am able to build a DLL out of my Winforms Application Project just by changing the Output type as "Class Library". But it is not happening in WPF and it is throwing errors if I do so. Is this the correct method of doing it or am I going wrong?
And in the Create New Project dialogue window, I am not able to find the .NET Framework selector drop down. After creating the project only I am able to change the .NET framework version by going inside the properties of the project.
Kindly help me to get out of this. Thanks in advance.
I have been working on this exact same problem for hours this morning. Here is what I think I have learned:
With Visual Studio Express 2013, it is by design that the WPF User Control Library template is not available for making a New Project. This is because it is the free Express version.
With the Express version, you don't have a "devenv.exe" for trying the "devenv /installvstemplates" to "fix" things. It is, instead, called (just a moment while I look this up again...) "WDExpress.exe" and will be located (if you have default location) in the "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE" directory. BUT - this won't help you. It won't fix your problem, because, as I mentioned, your Express installation is designed to not have that template available for New Project, so your "fix" won't put it there. I know this because this is what I tried myself. (Also, note that the instructions for doing this tell you to uninstall any extensions you've installed before doing it. And then, of course, if you still want them you have to reinstall them. Like I still have to do, incidentally.) I'm letting you know all of this so you don't go through the headache I'm having.
Note that I have not done this yet, so this is somewhat hypothetical on my part, but is based on my research on the Internet so far - Your solution is to create a WPF User Control Library manually [but now see UPDATE below]. (No, I don't know how to do this yet. I got into this in the first place, because I'm a WPF novice - just started working with it a few days ago - and late last night I got this great idea to add a "spinner" progress indicator to my "WPF play/learning project" I'm working on, and found a couple of relatively easy-to-work-with samples on the Internet - both of them are a WPF User Control Library - and at first I wanted to use the copy-and-paste to put the code in. But then I discovered... well, our mutual problem, because I'm using Visual Studio Express 2013. No such template under New Project. And literally at the tail end of my about-to-throw-in-the-towel, I'm googling and your post, Dhivakar, is already showing up with the right Google search.) So I haven't finished my research yet, but my next step is to learn exactly how to create a WPF User Control Library manually (the code and various project property settings), and then I can just save a WPF User Control Library skeleton for future use and document the details.
UPDATE: This guy totally has the solution for Express versions. I have followed his steps and it works great. The only additional piece of information I would add is that in my version (VSE2013), after you've created your WPF User Control Library template, when you open Visual Studio again and use File -> New Project, my selection in the tree (for a Windows app) came up under Templates -> Visual C# -> Windows (which is what I've been using). I did not see my template showing up there, after I created it, and I thought, "Great! Another piece of advice that doesn't work." But then I clicked up one on the "Visual C#" parent - and there was the template!
Here you go:
How to add a WPF control library template to Visual C# Express 2008
https://dotupdate.wordpress.com/2007/12/05/how-to-add-a-wpf-control-library-template-to-visual-c-express-2008/
Yes, it works this way for VSE2013 too.
UPDATE 2: I'm not absolutely positive about this, but I think he missed one little piece. In his step #4 he says to delete Window1.xaml and App.xaml. Maybe this didn't apply with VSE 2008, but in VSE 2013 there is also the App.config file which I believe is extraneous for our purpose. So you can delete App.config as well. As I said, I'm not absolutely certain about this yet, but I noticed that file in the project when I added a WPF User Control Library project to my solution, and I deleted it, and the solution compiled okay.
Try running devenv with the /installvstemplates switch, from https://msdn.microsoft.com/en-us/library/vstudio/ms247116(v=vs.100).aspx
If this doesn't work, browse to C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\ItemTemplatesCache\CSharp\WPF\1033\WPFUserControl (this could change dependent upon your installation directory), open the .vstemplate file in a text editor, and make sure the setting is set to true, then try running devenv with the switch again.
Hope it helps.