I need some guidance on how to have SpecFlow installed on my Visual Studio 2010 development machine which is also leveraged for SharePoint 2010 development.
The .feature extensions causes some bad behavior...
I just posted a version of SpecFlow that resolves this issue. You can get more info in this post.
What I had to do to resolve the issue was download the source and change the extension for the feature files to .sfeature.
I think the problem here might be that SharePoint 2010 and SpecFlow make use of the .feature file extension. I did some research into this and found a SpecFlow Google group query about a similar problem. The answer given to the user with the problem was:
Hi, I'm sure you know the SharePoint
project better then me. Do you see
any conceptual idea how this conflict
could be resolved? What parts are
conflicting, the syntax coloring or
the generation? Is the SharePoint
".feature" file can also be placed in
a normal c#/vbnet project?
Tips for
manual workarounds: to switch off the
automatic recognition of the .feature
file for the
genrator:
- rename key ".feature" to ".featureX" at "HKEY_LOCAL_MACHINE\SOFTWARE
\Microsoft\VisualStudio\10.0\Generators{FAE04EC1-301F-11D3-
BF4B-00C04F79EFBC}.feature" (this is
for C# projects)
you can still set the generation manually in VS by specifying
"SpecFlowSingleFileGenerator" for the
"custom tool" property of the file
to switch off syntax coloring:
remove (or rename) the shortcut at C:\Program Files\Microsoft Visual
Studio
10.0\Common7\IDE\Extensions\TechTalk\SpecFlow
Br, Gaspar
Maybe you could try the registry hack mentioned above and that might let you use SPecFLow with SharePoint?
The original thread can be found here:
http://groups.google.com/group/specflow/browse_thread/thread/4e6a80f3aa3624c2?pli=1
Related
I'm using InstallShield Limited Edition on VS2015.
I found several articles talking about an XML File Changes view, like this article, for instance.
However, I can't locate the view in LE. It might be due to the articles being a bit old and for a different version, or it might be that LE doesn't have this feature. I haven't found an article with the specific differences in features between the various versions of InstallShield, so my question is, can we do XML File Changes in LE? If yes, which view should I use to do it?
I installed InstallShield Express Edition, and while navigating the Help, I found the article entitled Upgrading to the Premier or Professional Editions of InstallShield. In it, you'll find the following:
Features that Are in Only the Premier and Professional Editions
(...)
Ability to modify text files or XML files—Use the Text File Changes view or the XML File Changes view to configure files that you want to modify on the target system at run time.
So this answers my question. Hope it helps someone else out there.
I have a project that was created using VS2102 Premium. When a co-worker tries to open it with VS2012 Professional he gets a "Needs migration" message for the project. Is this due to the different flavor of VS2012?
I wouldn't have thought so for most projects, however if you've used some feature of VS Premium that is not present in VS Professional, then I guess this is the response you'll get.
If you open a project from a previous version (eg 2010) then it'll offer to upgrade the solution.
You can manually edit the project, its only an XML file. Create a new blank project to see the structure and then use winmerge or similar to copy relevant lines across.
I am writing a VS2008 add-in that connects to a remote database blah blah.
I am having a problem with the app.config in this project. When I use SubSonic in my code, it moans that is cannot find the SubSonicServer section. This is because the .config file cannot be found.
This appears to a problem with paths as the add-in is a DLL running in the context of VS2008 and the working directory is C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE.
Is there a way to get the app.config to deploy properly with the application so my add-in (and SubSonic) can find what it needs in the .config file, or is there a way to get SubSonic to work without the need for the .config?
I am very experienced in SubSonic projects now, but only winforms, web, web service, and WPF applications. This is the first time I have tried to use SubSonic in a VS2008 Add-In project. I also have AppSettings in the config file which the ConfigurationManager cannot read because it cannot see the .config file.
2AM now and brain is tired of trying to figure this one out. Hopefully there is an answer when I wake up :)
TIA
My suggestion would be to not use the app.config file and inject the parameters at runtime.
I use this approach in my Subsonic 2.2 project:
http://www.digvijay.eu/digvijay.eu/post/2008/10/31/SubSonic-Trick-Specify-connection-string-at-runtime!.aspx
You might want to have a look at the answer to this question which deals with configuration for add-ins:
How to use app.config with Visual Studio add-in?
Resharper includes various analysis rules which can be run on your solution from inside Visual Studio but is it possible to run these from say the commandline or as part of your autobuild? Resharper seems to be focused on running in Visual Studio but can it be invoked on solution or project files from outside the IDE?
UPDATE: Seems like TeamCity 7.0 EAP includes a way to execute the code-analysis while building
(blog post) so at least it can somehow be invoked and utilized as part of a CI process.
No, this feature is not currently offered by ReSharper. There is a thread on the JetBrains website related to this question and it can be found here.
Here's a quote:
Currently ReSharper has no interface
from running in a standalone batch
application. However, it is possible
to write such an application that
provides the functionality you're
looking for using ReSharper OpenAPI.
So apparently you could use the ReSharper OpenAPI to create the functionality you want; unfortunately, I haven't had any experience in using it so I'm not much help there.
Some links of interest...
ReSharper OpenAPI Developer Community
ReSharper public API and sample source code (aka. ReSharper PowerToys)
I think you want the functionality provided by fxCop. I am not aware of Resharper functioning outside of Visual Studio.
Looks like they're listening! First version available as a 30-day demo now: http://blogs.jetbrains.com/dotnet/2013/03/resharper-code-analysis-goes-beyond-visual-studio/
If you're looking for compliance of code to standards, take a look at StyleCop. You can tie it into msbuild and run the rules outside of the IDE.
No, it can not be run from commandline. I still hope that they add this feature since I requested it last october :)
Does anyone use the MS SharePoint Solution Generator and VSeWSS 1.2 in a multi-developer environment with source safe? We are having issues re-deploying (because it doesn't really upgrade the solution with stsadm). It keeps saying the same feature is already installed - which it is, but it should retract the feature and re-install it - which it doesn't on some machines. Something is messed up with the feature's GUID but we can't find where that might be. One dev will be able to deploy and re-deploy but then the next dev won't. Where does VSeWSS 1.2 change the GUIDs? ARG!!!
We see the nice deployment targets (upgrade, etc) in STSDev but we're reluctant to use STSDev or the other codeplex tools because they are not supported by Microsoft. We have Visual Studio 2005 but not the money to upgrade to VS 2008 to get VSeWSS 1.3 - bummer.
---UPDATE----
I think we found a bug in VSeWSS that other's have commented on: Editing the projects properties resets some feature GUIDs.
It might also be a problem with the scope of the install. How do we get a site definition to install to the FARM scope in VSeWSS 1.2?
Don't worry too much about supported by Microsoft too much. While it is a consideration, the end result of MS SharePoint Solution Generator (terrible) and VSeWSS 1.2 are still SharePoint solutions and all solutions need to contain the same xml.
Could the deployment targets for STSDev be modified to work with your VSeWSS solution? After all, the deployment targets here are just working with STSAdm and a solution file.
In order to avoid the usual "works on my machine" you should set up a build and deployment system. If you are using virtual server or ESX server it should be fairly simply, and cheap as well. You should be able to use open source software all the way if you have more man power then money.
VSeWSS 1.2 and 1.3 store the feature GUID's in files in the /PKG directory of your Visual Studio solution. If you delete these files, or check our project into Source Control without these files and check them out on another machine, you will lose your GUIDs. Sure, VSeWSS will recreate the missing files for you, but it will do so with new GUIDs and new feature names.
A common requirement is to add the /PKG directory to your Visual Studio 2008 project and get it into source control.
You can read more about the files in the /PKG directory in the Release Notes for VSeWSS 1.3 here.
PS: We did some improvements to the Solution Generator in VSeWSS 1.3, but it wont generate a 100% perfect solution for you.