How do I copy my Layouts-o-Rama configuration to VS2013 now that I have upgraded?
Layouts-o-Rama is a brilliant Visual Studio extension when you find yourself using VS in different locations with different monitor setups. Just save a layout for each location/personality and create hot keys to toggle them.
It is good at what it does, but I just installed VS 2013 and I find that Layouts-o-Rama doesn't have the presets from VS2012.
It is possible. But it involves a few manual steps:
Install the plugin from the gallery in VS 2013
Copy over your settings:
c:\Users{username}\Documents\Visual Studio 2012\SettingsORama\
to
c:\Users{username}\Documents\Visual Studio 2013\SettingsORama\
Edit all of your settings files (for eg. "C:\Users\{username}\Documents\Visual Studio 2013\SettingsORama\2 monitors.vssettings") and change the ApplicationIdentity to 12.0 for VS 2013
<UserSettings>
<ApplicationIdentity version="12.0" />
Related
I have a solution that contains a .deployproj type of project. It seems that Visual Studio 2019 is not able to load that project. The detailed error message is the following:
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- Provisioning.Arm, "C:...\Provisioning.Arm\Provisioning.Arm.deployproj"
Non-functional changes required
Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.
What can I do in order to load the project within Visual Studio 2019?
It seems that you need to install the Azure Development workload in order for Visual Studio to be able to load .deployproj projects.
So just modify the current installation to also contain this workload. (I don't know exactly what individual component needs to be installed for this to work, I just installed the entire Azure Development workload).
I do have a TFS Project (TFS 2013) and I would like to set up my Visual Studio 2015 to work at that project. I have Visual Studio 2017 and Visual Studio 2015 installed. Now whenever I go to the main page of my Project and click "Open in Visual Studio" (like described here), Visual Studio 2017 opens. I would like to have it open in VSTO 2015. How can I select which version of Visual Studio should open?
The solution file should contain a UTF-8 signature that describes in which version the solution is to be opened. This is what's used for example to show different icons for solution files targeting different Visual Studio versions.
This signature info is also used by the Visual Studio Version Selector when opening a solution. An easy way to fix this is make sure that have the solution local on your dev machine and then right click -> open with and choose the Visual Studio Version Selector. Then pick the correct version of Visual Studio that you want to use.
This will then be honored by your browser when opening a solution since this also uses the Visual Studio Version Selector.
recently after build 2016 of Microsoft, I have install xamarin for visual studio 2015.
The key part of vs is its intellisense feature and that is not supported when working with .axml files.
Please suggest
Visual Studio supports Intellisense for Android .axml files, but you must enable this first. For enabling this feature, read How do I enable Intellisense in Android .axml files? - If you didn't find the files in the mentioned directory (see article), you could download these from GitHub:
android-layout-xml.xsd
schemas.android.com.apk.res.android.xsd
For Visual Studio 2015.
Link: https://forums.xamarin.com/discussion/60962/enable-intellisense-for-axml-missing-android-layout-xml-xsd-schemas-android-com-apk-res-androiod
Download "android-layout-xml.xsd" and "schemas.android.com.apk.res.android.xsd" from:
https://github.com/atsushieno/monodroid-schema-gen
Put all downloaded files into C:\Program Files (x86)\Microsoft Visual Studio 14.0\Xml\Schemas
Open .axml file and click XML/Schemas menu in the Visual Studio. Then add correspondent files to the project.
Xamarin for Visual Studio includes out of the box xsd-based intellisense support starting with our cycle 7 builds. (XamarinVS 4.1.0.x).
You can try it right now switching to the Beta channel. In Visual Studio go to:
Tools - Options - Xamarin - Other
Select the Beta channel, and press Check now
Keep in mind that if you're developing for Xamarin.iOS, you will need to switch to the Beta channel your Mac as well. That can be done from Xamarin Studio in the Mac.
This is for Visual Studio, but you need a Xamarin Studio installation to make it work.
To enable Intellisense in Android .axml files:
Download or copy android-layout-xml.xsd into Visual Studio folder\Xml\Schemas
open catalog.xml and add line after last :
http://schemas.android.com/apk/res/android' />
Save catalog.xml and restart (or start) Visual Studio.
Intellisense in .axml files should work by default. (Maybe you need add a schemas.android.com.apk.res.android.xsd file too.)
Shem's files: https://github.com/atsushieno/monodroid-schema-gen
Visual Studio 2013 Premium Update 4; Visual Studio 2013 SDK installed.
I see the code sources are for older Visual Stuido version. It has a link to Visual Studio 2010 (instead of 2013) SDK Samples.zip file. I try compile its some projects but I get an exceptions... For example:
Other projects compiled successfully, but I read their instruction of running:
Running the Sample
To run this sample, copy both the
AlphaBlendToolbar.Addin file and the newly-built AlphaBlendToolbar.dll
file into your Visual Studio Addins directory (My Documents\Visual
Studio 2010\Addins) and then open a new instance of Visual Studio
2010. Next, run the Tools | Add-in Manager menu command. Check the checkbox next to AlphaBlendToolbar and hit OK. You should see a new
toolbar with two command buttons on it. The interesting thing about
this sample is that the command button icons have alpha-transparency.
But VS 2013 has not the Addins directory... Ok, I create it:
I compiled the sample of SDK:
but I don't see here the compiled DLL:
Why I have such problems?
The AddIns folder under the Documents folder is not created by default by VS when installed, so you need to create it by hand, as you have done
Remove the folder C:\Users\developer\Documents\Visual Studio 2013\AddIns from the Options window, it is not required, the %VSMYDOCUMENTS%\AddIns folder takes care.
.AddIn files can contain several values to describe the target VS versions. The AlphaBlendToolbar.AddIn file of the sample only contains the VS 2010 target, you need to edit it and add the VS 2013 ("12.0") target:
<HostApplication>
<Name>Microsoft Visual Studio</Name>
<Version>12.0</Version>
</HostApplication>
Notice that there are two .AddIn files, one in the Documents folder (for deployment) and other in your solution (for source control, etc.), ensure that you update both.
FWIW, there is a VS 2013 SDK Samples: http://blogs.msdn.com/b/vsx/archive/2014/05/30/vs-2013-sdk-samples-released.aspx
I installed the free version of ApexSQL which is awesome in SSMS, but I really don't want all those menus in Visual Studio. I went to add-in manager and unchecked them, but the Startup column is checked and disabled so every time I restart Visual Studio they come back.
Is it possible to permanently remove the ApexSQL menus from Visual Studio?
If you have ApexSql installed and you don't want those pesky menus in Visual Studio do 2 things.
In Visual Studio, go to Tools > Add-in Manager and uncheck the ApexSql addins. Close Visual Studio.
In Windows 7, there's a hidden folder C:\ProgramData. In Windows Explorer go to C:\ProgramData\Microsoft\MSEnvShared\AddIns folder. Edit each of the *.MsvsLoader.Addin files and set <LoadBehavior> to 0. If you can't save the files directly, you'll have to save the files to a different location (desktop maybe) and then copy them back into C:\ProgramData\Microsoft\MSEnvShared\AddIns because there's some Admin privilege required.
Now when you restart VS those ApexSQL menus should be gone
The issue of crowding menus is resolved in latest releases, now all ApexSQL add-ins are under the main ApexSQL menu as sub-menus. They look like this now:
If you don't need ApexSQL add-ins in VS or SSMS you can simply choose not to integrate them with VS or SSMS during the installation, just check out SSMS ot VS version in which you want the add-ins integrated
Note: To get this dialog in which you can check the wanted integration you need to use individual installers not the main one. You can find all individual installers on this link
Disclaimer: I work for ApexSQL as a Support Engineer
For Visual Studio 2010 on Windows 7, I attempted #Chris Bayles suggestion and do not see ApexSql addins under Tools->Add-in Manager.
I followed #Jerome2606's pointer to https://knowledgebase.apexsql.com/remove-add-ins-just-visual-studio-retaining-sql-server-management-studio/ and it worked for me, but only when I removed the parent ApexSQL folder as well.
Summary of what is required to do:
Remove folder
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\ApexSQL
Depending on the version of Visual Studio, the version number in the default installation location will be different:
Product name Version number
Visual Studio 2010 Microsoft Visual Studio 10.0
Visual Studio 2012 Microsoft Visual Studio 11.0
Visual Studio 2013 Microsoft Visual Studio 12.0
Visual Studio 2015 Microsoft Visual Studio 14.0
Select and delete the ApexSQL folder and its contents.
Open Command Prompt as an administrator, then run
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe" /setup
Please note the command is different for Visual Studio 2012, 2013, and 2015.
If you are using SSMS v18.0 then you can disable the apex features in following way.
You can find the ApexSQL.Complete.Addin.SSMS18.pkgdef file from following path.
C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Extensions\ApexSQL Complete
Then open this file in Notepad++ Administrator mode and comment the content.
If you need further reading follow this link.
https://knowledgebase.apexsql.com/remove-apexsql-tools-sql-server-management-studio/