I would like to give guidance for my team. With VS.NET 2k5 and 2k8 we had Guidance Automation but now it's gone.
I know the free alternative (Open GAT/GAX) but I dont really like it.
As far I know T4 templates are not good choice for that.
What we need:
fix type: class library
setting build output
creating namespaces, folders
creating files
See GAX 2010 For Visual Studio 2013 and GAT 2010 for Visual Studio 2013, both by Jelle Druyts.
I haven't used either one (I used GAT/GAX back some years ago, along with the Web Service Software Factory), but I look forward to hearing from you how well they work.
Related
I am trying to migrate legacy code, consisting of thousand of lines code from visual studio 2005 to visual studio 2015.We have searched all over the internet but haven't found any useful resource.Can anyone please help us regarding this??
May be it will help you:
According to article "Many widely used assets behave the same in Visual Studio 2015, Visual Studio 2013 and the two earlier versions". You may need convert to VS2012 and use it in VS2015.
Did you test this: github?
In the internet there are some articles migrate for example: VS2005 to VS2008 and VS2008 to VS2012. Try to use 2 step conversions.
The best way to manually migrate: create empty project in VS2012, move your files from the old projects
Can I create ASP.NET-5 projects in Visual Studio 2013 somehow?
Also share please links with documentation, examples or anything that could help to create project using mvc6 that used to be on web api.
The simple answer is not. I'm pretty sure, vNext is such big change in Microsoft technologies that they will not put any effort in adding that vs2013, you can get vs2015 community edition is very complete free version of visual studio.
this link is very good starting point.
I am trying to develop custom code for an InfoPath 2013 form. I have Visual Studio 2013 Professional installed, but when trying to edit code I get the following message:
The following external components are required to edit your form code. Please install them and try again.
Microsoft Visual Studio 2012
Visual Studio C# Support
Microsoft Visual Studio Tools for Applications 2012
C# support is installed, along with Visual Studio Tools for Applications 2012.
Does InfoPath 2013 just not support VS2013?
Unfortunately No
MS has really been making some bad decisions lately
Firstly VS2013 was released so they forced people to upgrade if you want to develop for Windows 8.1
Secondly, MS have announced that they are dropping InfoPath and have yet to provide an alternate solution. Support is still available but InfoPath 2013's successor will be another solution.....i'm guessing Azure Forms or SharePoint forms, something like that
Very disappointing
As you have found, adding code to an InfoPath 2013 form requires Visual Studio 2012. I am not aware of a way to use it with any other version of Visual Studio.
Depending on what you plan to use the custom code for, you may be able to get by with the qRules library (full disclosure: I am one of the developers of this library). It contains many of the most common features for which people tend to use code within InfoPath, and you can use them simply by executing rules within your form, eliminating the need for any version of Visual Studio.
If there is a specific thing you are looking to do with code, I can tell you whether it's possible to do so with qRules, but you should open a separate question for that (and let me know here).
This question already has answers here:
Closed 12 years ago.
Possible Duplicate:
What are people replacing the missing C++/CLI Intellisense in VS 2010 with?
I downloaded and installed Visual C++ 2010 Express, today. To my shock and horror, a variable's dot was not followed with anything, an error at the bottom status bar reading:
"Intellisense: Unavailable for C++/CLI"
So... that being the case, is there an alternative to Intellisense that I can find and use? Other stackoverflow questions addressed the possibly broken nature of Intellisense. From what I've read, though:
They suggest Visual Assist. Visual Assist's free trial, as I just downloaded, is not compatible with VC++ 2010 Express.
They talk about manipulating Visual C++ itself somehow, usually through the deleting of a .ncb file. Do any of you know where this file is located? If so, that's one answer I'm hoping for -- maybe it'll fix intellisense!
Thanks! Of course, feel free to chime in with any other ideas!
Yes, VS 2010 doesn't support C++/CLI Intellisense. The VS team promised it would come with an update, but I'm quite sure we won't see it. Too bad, C++/CLI is amazing for creating bridge classes between C++ and C#/VB/any other .NET managed laguage.
Visual Assist X indeed brings it back, but since VS Express editions don't support extensions, you have three options:
1) Live without Intellisense
2) Get VS Professional or better (if you are student, you can get it from MSDNAA for free)
3) Downgrade to Visual C++ 2008 Express
Just use Visual Studio 2008.
It's a simple matter of which feature you find more important. Pick only one:
Multiple monitor support
Intellisense for C++/CLI projects
This is easily one of the most annoying "features" of Visual Studio in its history and I don't understand why it exists -- ever.
Why would a CodePlex project need to care what version of Visual Studio I am using?
Off the top of my head, the only thing I can think of is that some versions of Visual Studio might introspect assemblies searching for attributes to determine what to display in "Visual Designers" and "Property Editors". But why would that cause Visual Studio to not be able to open the project and allow me to browse its contents and compile?
It seems to me like Open Source in .NET is somewhat limited by the stupid dependency management exhibited by Visual Studio. In other words, if I am using Visual Studio 2008 and you are using Visual Studio 2010, then we have different solution files.
http://blogs.msdn.com/b/visualstudio/archive/2010/03/15/why-does-visual-studio-2010-convert-my-projects.aspx
Here's an example from the site as to why Visual Studio converts your projects to 2010 format.
For instance, Visual Studio runs
custom tools such as single file
generators for designers in order to
output code representing the changes
made to the designer. Many of these
custom tools are upgraded or
completely replaced in the newer IDE.
During conversion, the IDE knows which
custom tools to replace or upgrade. In
order to make round-tripping work, VS
would need old and new custom tools to
understand each other so as to ensure
that old and new designers can work
side by side. Other than designers,
the following files would also be
affected: resource editors, wizards,
code snippets, item and project
templates, diagramming and modeling
tools, and many more.tools, and many more.
Since 2010 knows about what tools 2008 has, it can convert forward to be compatible with the custom tools 2010 uses. 2008 has no idea about what 2010 is using, how could it? Therefore, it is impossible to convert backwards since it doesn't know what it needs to convert, nor how to.
I believe the purpose of this touches on what you stated in your comments. If you are using 2008 and I 2010 and I compile it, how could you possibly run it again? 2010 is backwards compatible but 2008 has no way to make itself forward compatible.
Thus, by recompiling the project in 2010 I ensure that no 2008 user may mistakenly think they can compile it.