I try to find out what is the best way to develop react app with .net web api as the api service.
I realized that using visual studio 2015 won't work since its lack of es6 support.
I really liked atom as the "client" side programming and visual studio 2015 but I foresee issues working with 2 IDEs opened, especially for those whose computer is not strong enough..
I have also heard of visual studio code but I don't have much experience with it and how exactly to debug in it.
Would like to here your suggestions, thanks
You can try to use Rider from jetbrains - A fast & powerful,
cross-platform .NET IDE.
I use that IDE daily and have support for ES6 and JSX Typescript and more.
Related
I'm porting all my development to Visual Studio 2017. I made heavy use of Portable Libraries in 2015, but it appears that .NET Standard is the way to handle cross-environment issues going forward. I've got a single file code generation extension that I've upgraded. In Visual Studio 2017, it works great against the traditional .NET libraries and portable libraries, but it doesn't work with the new .NET Standard library I'm trying to build. I'm happy to consider that I've done something wrong, but the GITHUB example doesn't work either:
https://github.com/Microsoft/VSSDK-Extensibility-Samples/tree/master/Single_File_Generator
Anyone know why Visual Studio extensions (at least code generation extensions) don't work on this project type?
There is no Coded UI project in Visual Studio 2015 for UWP and I can't find any documentation anywhere saying there is a plan to bring support.
Does anyone know if there is planned support it or have some alternative UI testing framework to work with Windows Universal?
I guess you can use this Coded UI Test Project (Universal Windows) which is under
File->New->Project->Templates->Windows->Universal-->Coded UI Test Project (Universal Windows)
for Coded UI project in Visual Studio 2015 for UWP.
Maybe an important information for other to come is. That it’s not possible to create such projects in the community version of visual studio. You need at least the enterprise version as mentioned here.
An update for anyone arriving at this question is that Microsoft are deprecating support for Coded UI testing after the Visual Studio 2019 release...
https://learn.microsoft.com/en-us/visualstudio/test/use-ui-automation-to-test-your-code?view=vs-2017
Coded UI Test for automated UI-driven functional testing is deprecated. Visual Studio 2019 is the last version where Coded UI Test will be available. We recommend using Selenium for testing web apps and Appium with WinAppDriver for testing desktop and UWP apps.
So, the suggested answer by Microsoft for automating UWP UI testing is to adopt Appium with WinAppDriver.
I've been given the task of developing some extensions for Visual Studio for our internal use. These will have to support a couple of different versions of Visual Studio (VS2008, 2010 and 2012 - VS2005 would be a nice to have but not essential). I'd like to develop these in as consistent a way as possible, reusing as much of the code as possible, while fitting it into the existing project structure for these kinds of tools, which is a Visual Studio 2012 .sln.
What's the best / easiest way of developing this kind of extension? A VSPackage project? Can I make a 2008-compatible VSPackage which is developed in VS2012?
The features I will need for the extensions I'm writing at the moment are pretty basic - I need to create Tools menu commands, possibly a custom toolwindow. My requirements might change later on but I don't need editor adornments or anything like that at the moment.
I saw this question which might seem to be a duplicate, but the answer which was accepted doesn't answer the question, so...
It really depends on what is your extension going to do.
VS2008 does not support extensions (.vsix) and you will need to write VSPackage deployed as msi for it. You also won't have access to many new features introduced in VS2010 (easier editor integration and access to vs services via MEF), but basic stuff such as manipulating solution/project/files should be fine and work on all versions (e.g. using DTE should be ok).
As far as I remember for VS2008 you will also need to obtain a PLK, which is no longer required for 2010 and 2012.
I haven't tried developing 2008 package in VS2012, but you definitely can develop 2010 extension in 2012.
Also remember that VS2008 is .Net 3.5, so your code should use .net 3.5 and version of c# which it supports to be portable.
Where can I find a bug-tracking system that integrates with Visual Studio 2010 as an addin, and supports online support (so that anonymous people can add bugs to the buglist)?
You could use TFS and write a simple web frontend utilizing the TFS webservices. Perhaps there are bugtrackers that support TFS integration.
Unfortunately, I do not know of other solutions integrated into VS.
I ended up building my own system based on a database and a webserver. I then created a Visual Studio Package (add-in) through the Visual Studio 2010 SDK for managing bugs that were synced live from the website.
Way better for my needs, and only took 1 week of development.
I'm considering developing a medium-size project for a client in IronPython. It's a pretty straightforward replacement for an existing system I've been supporting for several years, so the specification is quite well defined and understood.
This is my first significant IronPython and .Net project so I'm expecting a bit of a learning curve. I was going to use SharpeDevelop, but I can purchase VisualStudion 2010 for a reasonable price and whilst I understood that IronPython Tools for Visual Studio 2008 were not so good, I haven't seen anything about the update for 2010 yet.
Has anyone used either or both of these in a reasonable-sized commercial environment and do you have any recommendations?
(and I'm aware of this question, but this is specifically about VS2010)
Here is a quick comparison of IronPython Tools for Visual Studio 2010 and SharpDevelop showing the features that one has which the other does not:
IronPython Tools for Visual Studio 2010 has:
Better intellisense.
WPF designer.
Can edit your code without a project.
Go to definition support.
Find all references support.
More comprehensive IronPython interactive window integration.
SharpDevelop has:
WinForms designer.
Code conversion support from C#, VB.NET to Python
Compiles your IronPython code to an executable or class library.
Both of them are free. You can use IronPython Tools with the Visual Studio 2010 Shell (Integrated) which is a free download.
Considering that the IronPython Tools for VS2010 are "only" at the CTP stage, they're very high quality (anyone else would call them a beta). I've been using them when I can for a while now and haven't had any major issues. If you do have any issues with the VS2010 tools, the IronPython team is very open to feedback.
I haven't used SharpDevelop's tools, however, so I can't really compare them.
Greetings;
From what I've followed and read on-line during the Visual Studio 2010 Beta program and after, there seems to be no direct IDE support for IronPython in Visual Studio .NET 2010:
http://www.itwriting.com/blog/2158-why-f-rather-than-ironpython-in-visual-studio-2010.html
However, there is a Dynamic Language Runtime Support for the .NET 4.0 Framework using IronPython through a stable release of IronPython 2.6.1 on CodePlex:
http://ironpython.codeplex.com/releases/view/36280, but again, there is no direct support for the Visual Studio .NET 2010 IDE.
As for IronPython support in SharpDevelop, the IDE has full support for WinForms and Console based applications, and debugger support for IronPython, including 2.6.1 and the .NET 4.0 Runtime beginning with SharpDevelop 3.2 RTW. Matt Ward, who has headed up the IronPython and SharpDevelop IDE integration efforts has been very active and helpful through the forums and his blog entries. I was working on a small project in IronPython using SharpDevelop, and for the questions and bug that I found during SharpDevelop 3.0 Beta 1, Matt's support and turnaound time for IronPython issues was tremendous.
With this in mind, if you're looking for the productivity gains of using an IDE, with source code debugging support for IronPython applications and all of the benefits of using the .NET 4.0 Framework and DLR Support, you may want to start with SharpDevelop.
I hope this was of help...