VS2010 and DSL deployment - visual-studio-2010

Can anybody help me on this? I want some guide on how to deploy DSL in vs2010, i use the VSIX output that is in DSLPackageProject\Bin\Debug but when then i want to add that item to some project(File->Add New Item) it just adds dsl but without any DSL functionality that is available in experimental hive,
Many Thanks,
Hrayr

This issue is related to the Beta 1 of Visual Studio, if you install the Beta 2 you will be able to deploy your DSL correctly

Related

How to Configure Specflow 3.0.199 with NUnit 3.11?

I have done this a couple of times before, but it's not working today. Am I missing something?
I want to configure Specflow from the scract, using NUnit and to execute inside Visual Studio.
I've seen many tutorials but they are not working to me :P. I'm trying to use the latest versions.
These are the steps I'm doing on Visual Studio 2017:
Create a test project (.NET Framework)
Install Specflow plugin for Visual Studio (Tools > Extensions and Updates)
Delete reference of MSTests from the nuget packages.
Install SpecFlow 3.0.199
Install NUnit 3.11
Install SpecRun.Runner 3.0.284
After creating a default feature file and generate its steps, when I compile the solution I get this error on CalculatorFeature.feature.cs (the generated file):
It's like those configurations are not compatible. What's going on?
If you have another step by step list, let me know how to configure Specflow with NUnit to run on Visual Studio 2017, please.
For SpecFlow 3 you have to use the MSBuild generation.
To this, follow these two steps:
Add the NuGet package SpecFlow.Tools.MsBuild.Generation with the same version as SpecFlow to your project
Remove all SpecFlowSingleFileGenerator custom tool entries from your feature files.
From https://specflow.org/2019/generating-code-behind-files-using-msbuild/
Background what is happening:
The VS Extension has sometimes problems to find the used SpecFlow version. In that case, it falls back to the SpecFlow version shipped with the extension (which is really old). This version is generating code with now not existing NUnit attributes.
TestFixtureSetUp and TestFixtureTearDown attributes were deprecated for quite some time and were finally removed. They are replaced by OneTimeSetUp and OneTimeTearDown.
Your choices are probably...
Go back to an NUnit version that supports the old attributes.
Get a version of SpecFlow that uses the new attributes.
Find a way to configure SpecFlow and tell it to use the new attributes. Sorry, but this option, which is no doubt the best, is out of my wheelhouse.

Create DSL Package in visual studio 2010

I have a DSL project for VS2005(Active Writer Customized) .I want to make it compatible with VS2010.So
I migrated the project with DslProjectsMigrationTool.exe which comes with vs2010 SDK.
Created new dsl project in vs2010 and moved my migrated codes to the new project.
Here my Dsl project is building fine.But DslPackage project is showing the following build error.
Error 48 : No Visual Studio registration attribute found in this assembly.
But some blogs relates this error to RegPkg.And i don't have any idea about RegPkg.
Any solutions to resolve build error?
This looks like it could be to do with the RegPkg version. Perhaps try the solution discussed here, which effectively uses Reflector to check which version of RegPkg is expected.

Configuration Section Designer alternative

The project Configuration Section Designer http://csd.codeplex.com is such a great tool but now I've moved to VS2010 (forced actually) and it doesn't support 2010. I use this tool a great deal but now I can't and I have a ton of config stuff to write.
Is there an alternative to this tool that will work with VS2010?
I'm hoping for a good solution and not having to do a project in VS2008 and manually import the generated files. Ugh, the thought of using appSettings to store configuration is just horrid.
I was recently added as a contributor to this project (andym1978). I was able to fix the code to support VisualStudio 2010. We want to do more testing before releasing to the official 2.0 downloads area, but I've uploaded an unofficial 2.0 release
HERE. Please report bugs to the issues page and I will get to them ASAP.
There is an open discussion regrading this matter.
currently it seems like there is no formal version that is built for vs2010.
more information here : http://csd.codeplex.com/discussions/73703?ProjectName=csd
The version for VS 2010 is now available.
http://csd.codeplex.com/

How to set the default .Net framework version for projects in visual studio 2010

How do you set the default framework version for new projects in Visual Studio 2010?
The easiest way I know of is the following
File -> New Project
Select the Framework you want
Create the project
From then on the new project dialog will default to the framework you selected in step #2.
I know that this is a very old question but I needed the answer to it several times now and I keep searching for it. So, I will share my experience here and hopefully in the future I would not need to search for it too long and those who are looking for the same can find it too. I just tested it with Visual Studio 2015. Open the registry hive HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\14.0\NewProjectDialog and look for the value FxVersion (REG_SZ type). For me it used to be 4.6.1 and I changed it to 4.6.2. Now when I create a new projects they target .NET v.4.6.2 by default.

Error upgrading WSSF solution to VS 2010

I've recently installed VS2010 and I'm trying to upgrade a project that I created using VS2008 and WSSF (Web Service Software Factory). I've installed the 2010 version of WSSF and it's prerequisites. After upgrading, when I try to load the solution I get "blah.ssfproduct cannot be opened because its project type (.ssfproduct) is not supported by this version of the application". Absolutely no idea what to do :(
Cheers
Mark
The Service Factory for VS2008 has a custom project that holds the model files and the VS migration wizard doesn't know what to do with it. Fortunately, the 2010 version has changed this custom project to a normal C# class library project and all the model files can be added to it ('Add Existing") without modification. For the final release, we will include the few migration steps to keep everyone out of the woods. Sorry for not supplying it with our pre-release drops.
In case you haven't seen it, your question was also answered by a community member on the Service Factory community at http://servicefactory.codeplex.com/Thread/View.aspx?ThreadId=211726. The response includes steps that worked for one person and they seem solid to me too.
Cheers,
Don

Resources