I try to make SlowCheetah work, but when I open the VSIX File, I get just th VS 2010 as Selection.
If I check the File, I definitely see:
<VisualStudio Version="12.0">
<Edition>Ultimate</Edition>
<Edition>Premium</Edition>
<Edition>Pro</Edition>
</VisualStudio>
</SupportedProducts>
And we have Premium 2013.
Is there anything else I need to be aware of?
Related
I am running VS 2015 and VS 2017 side-by-side. I have installed TechTalk's SpecFlow from Nuget plus Nunit, the same on both VS versions. When I try to Add New Item a new feature file I can do this on VS 2015 but on VS 2017 I can't see the SpecFlow feature template, or, indeed, any SpecFlow template. The reference to specflow is definitely in the references; there's a configsetting in the app.config for Specflow.
How do I start with SpecFlow in VS 2017 [v15.2 (26430.16) Release; .NET 4.6.01055; SpecFlow v2.2.0] ? Is SpecFlow even usable on VS 2017?
For item templates, intellisense and some other features you need to install the SpecFlow Visual Studio Extension in Visual Studio.
Extension for VS 2015: https://marketplace.visualstudio.com/items?itemName=TechTalkSpecFlowTeam.SpecFlowforVisualStudio2015
Extension for VS 2017: https://marketplace.visualstudio.com/items?itemName=TechTalkSpecFlowTeam.SpecFlowforVisualStudio2017
After installation you have the item templates available.
Andreas' answer is correct - the answer is to install the extension. However, the Download button on the URL above seems to do nothing, so it's best to install the extension from Visual Studio (select “Tools”, “Extensions and Updates…” from the menu. Click on "Online" on the left, and search for "SpecFlow") Make sure all your open instances of VS are closed down to complete the installation, then 'Modify'.
to use specflow in VS:
you need to install specflow extension (for your VS version)
then install specflow nuget package
it's better to restart VS in between.
for version < 3, then make sure you have "Enable SpecflowSingleFile Generator" set to false in (tools>options>specflow)
for version 3 onward, set to true
I'm trying to integrate starcounter with visual studio 2013 by installing starcounter but this is not happening, how do I integrate with visual, after integrating how to create a simple project with starcounter.Thanks in advanced.
Starcounter 2.3 and newer does not support Visual Studio 2013 anymore, as presented on the https://starcounter.io/download/ page ("System Requirements"). Currently VS 2015 and 2017 are supported.
I think the only thing that needs to be integrated is creating a project from the template. Building is done by MSBuild, so I don't think VS version affects it.
Try to copy an existing project (e.g. https://github.com/StarcounterApps/KitchenSink) and change it to your liking. You will need to do some manual steps to add new pages:
Open your csproj file in an editor
add an entry for json file
<ItemGroup>
<TypedJSON Include="RadioPage.json">
<Generator>MsBuild:Compile</Generator>
</TypedJSON>
</ItemGroup>
add an entry for code-behind
<Compile Include="RadioPage.json.cs">
<DependentUpon>RadioPage.json</DependentUpon>
</Compile>
There may be a way to do this in a less manual way, but I don't know how to add dependent file in VS
In the docs, you can see how the Starcounter templates look and read how to use Starcounter without Visual Studio or the extension.
In short, it's no problem using Starcounter with Visual Studio 2013, although, you will miss out on some of the benefits that the extension come with.
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
After testing and uploading release 2.4 of my extension SwitchStartupProject (source code) to the Visual Studio Gallery, I noticed that in VS 2013 it neither appears in the extension search results when searching with appropriate keywords (e.g. switch startup), nor does it show up as available update when an earlier version of it is already installed.
But the extension works in VS 2013 when its VSIX file is downloaded and installed. Also the Visual Studio Gallery page shows that it supports VS 2013. And in VS 2012 and VS 2010 both search and update indication works.
The extension supports VS versions 2010, 2012, 2013 (and 2014 CTP) using a version 1 VSIX manifest:
...
<SupportedProducts>
<VisualStudio Version="10.0">
<Edition>Ultimate</Edition>
<Edition>Premium</Edition>
<Edition>Pro</Edition>
</VisualStudio>
<VisualStudio Version="11.0">
<Edition>Ultimate</Edition>
<Edition>Premium</Edition>
<Edition>Pro</Edition>
</VisualStudio>
<VisualStudio Version="12.0">
<Edition>Ultimate</Edition>
<Edition>Premium</Edition>
<Edition>Pro</Edition>
</VisualStudio>
<VisualStudio Version="14.0">
<Edition>Ultimate</Edition>
<Edition>Premium</Edition>
<Edition>Pro</Edition>
</VisualStudio>
</SupportedProducts>
...
Any idea how to make it appear in VS 2013 extension search?
At the moment there is a bug in the Visual Studio Gallery which stops extensions from being seen in 2013 if they have support for Dev14. This has been going on for a few weeks now and there hasn't been any status updates on the issue (or a even a public acknowledgement that such an issue exists).
The best work around at the moment is to publish your extension on the gallery twice
The normal project without Dev14 support
A special temporary version of the project which supports only Dev14
This is the approach I've been taking with VsVim.
A fix was deployed today which should resolve this issue.
I see that PowerCommands for Visual Studio 2010 supports visual studio 2012, but it was last updated in Aug 2010. Is there a new "PowerCommands for Visual Studio 2012" or is there a viable replacement?
You don't need a replacement. If you install the Power Commands again, from within VS 2012 (Tools -> Extensions and Updates), it will be applied to VS 2012.
From here:
Just reinstall, even if you already have it for VS2010. The reinstall will then apply it to VS 11
I just did it, and it worked perfectly.
Edit
Productivity Power Tools
Microsoft Visual Studio Team Foundation Server 2012 Update 1 Power Tools
For Visual Studio 2013, it looks like Power Commands is now part of Power Productivity Tools.
I ended up using VSCommands for Visual Studio 2012. This tool provided all I needed from PowerCommands and more.
Most of what was in the Productivity Power Tools are now part of VS 2012. There are a few items missing, afaik, what are you looking for in particular ?
As mentioned on the Productivity Power Tools 2012 page, the Power Commands were added to that addon.
Download the VS2010/2012 version from the VS Gallery.
Unzip the .vsix to a folder (i.e. using the great 7zip), it's just a zip file.
Edit the extension.vsixmanifest file and add this element after the 11.0 one:
<VisualStudio Version="12.0">
<Edition>Pro</Edition>
</VisualStudio>
Repeat for every future version of VS that comes out ;)
Now re-zip the contents (files, not the root folder, so that the extension.vsixmanifest is at the root of the zip file, not within a folder), rename the zip file to .vsix, and double-click to install to all your newly supported editions.
Enjoy!