Is there any way to get any support for jsx-syntax in visual studio? preferably for both .js- and .jsx-files
All I get now is squiggly lines over the shop, so anything better than that would be great
I dont want another IDE just for my react code. (ie, I know about VS Code.)
Is there any way to get any support for jsx-syntax in visual studio 2017?
Related
So, I am trying to follow along with a video in order to help myself with a project I have soon. When following this project I recognize that my visual studios is different. In the video it shows a "create a new project" window along with different templates like "Console App" and "ASP.NET core web app". While on mine, I am not able to see any templates. I have tried looking up other ways to find these templates, but I have yet to find it. I am hoping someone can help me figure out what I am missing on my visual studios. Below is the video visual studios and the second picture is my visual studios(macbook).
Video Visual Studios:
My Visual Studios:
I think that you failed the download. The video you're watching is using Visual studio, but you are using Visual Studio Code. You should change and download Visual studio.
Is there any way to get any support for jsx-syntax in visual studio?
preferably for both .js- and .jsx-files
All I get now is squiggly lines over the shop, so anything better than that would be great
I specifically wrote that I not want another IDE just for my react code. For some reason it disappeared from the final text... Now, as the Title suggests:
Is there any way to get any support for jsx-syntax in visual studio 2017?
Is there a way to debug AngularJS code in Visual Studio?
Note: I'm not talking about VS Code.
I would like to be able to set breakpoints and see what's happening there.
I'm aware of other IDE-s which allow us to do that.
So is it possible to use Visual Studio IDE for that?
put break point in visual studio(Angularjs code) and run your application in IE so that break point will hit into visual studio
Nowadays we can use Edge as well instead of IE. That is a better solution since it's chromium based and has less issues compared to IE.
I just installed Visual Studio 2017 Enterprise and selected Desktop-Development for .net features.
Now when I'm starting up Visual Studio and create a new WPF project, theres no advanced objects in the toolbox like the arc Control or more Effects other than BlurEffect and DropShadowEffect. These and many others are just missing. When I look in the object browser in Visual Studio Blend, I can't find them there either.
Do I need to install something else explicitly?
Okay so I found it out: You have to manually select "Blend for Visual Studio SDK for .NET" in the Components section of the installer. This will actually install all the advanced WPF Controls, which where missing for me.
Those where always installed from VS Installer versions 2012, 2013 and 2015 automatically (its a package of 100mb).
I can just imagine that the Idea of a much more modular installer led the designers there to think "we need to make the installation faster so push out every little package that was used commonly throughout the last 5 years.".
And then they thought: "BUT hey, when it comes to the Xamarin installation, let's KEEP IN all the Google-Emulators for Android which pack a WHOPPING 17 GB!!!"
They surely thought also: "Most people wont need these, since they either have a android device on their own or they use one of our emulators, which are vtx enabled, so 10 times faster than googles emulators, and ours also only need 1 GB of disk-space. But well, we wanted to make a fast installer after all, so let it pack our customers drives full of stuff they don't need at all".
You can right-click on a category in the toolbox and click on the "Choose items" option and try to find the tools that you are missing:
visual studio 2010 toolbox standard controls missing
Blend is more design friendly than Visual Studio though so you shouldn't be suprised if you see more options in Blend. After all, Visual Studio is a programming/coding tool and Blend is a design tool.
You rarely (or never) use the toolbox to add elements to a WPF view in a "real-world scenario. In fact it is quote common to disable the designer altogether: http://blog.spinthemoose.com/2013/03/24/disable-the-xaml-designer-in-visual-studio/. If you are a serious WPF developer you should really learn XAML and MVVM :)
I need to create a WPF app using the Surface SDK. I am using Visual Studio 2012, and according to this SO post, VS2012 doesn't allow that. However, since this was posted before it was officially released, I want to make sure I'm not missing something.
I just need a few of the touch/swipe controls that come with it. Is there a different option for VS2012? The other developer is using 2010, so it needs to be able to still run on his machine. It's a very simple app that I just need to hammer out, so I'm looking for the fastest, easiest method. Both of us and the end application is to run on Windows 7.
I found an easy solution by which it seems to work. It does expect you to have Visual Studio 2010 installed. Following the following steps I managed to compile in Visual Studio 2012 using .NET 4.5. TouchDown events work. I tried it out on some small projects and they seem to work perfectly fine.
Use Visual Studio 2010 to set up a Surface project.
Safe and close Visual Studio 2010.
Open the solution using Visual Studio 2012.
Change the target framework under project settings to .NET 4.5.
Save as a new solution file.
Compile, ... everything works!
This method prevents you from having to set up all the configuration files/references yourself. The only downside is you don't have any of the Surface tools integrated into the IDE. E.g. the toolbox, project templates, ... This of course doesn't prevent you from writing plain XAML yourself.
If for some reason this doesn't work in the long run I will update this post.
The easiest way will unfortunately be for you to run VS2010.
Currently the SDK is not supported in VS2012, for a few reasons.
Notably, the way that touch works in Win8 is a lot better than in previous versions of Windows. This unfortunately meant a rewrite of the touch layer that the Surface SDK uses. The new controls are written to adapt dynamically based on mouse/touch input, making the Surface SDK controls a bit redundant.
Microsoft might make the SDK available for VS2012 in the future, but this is kind of debatable.
If you are still dead set on giving it a shot, download an application called Orca (http://msdn.microsoft.com/en-us/library/windows/desktop/aa370557(v=vs.85).aspx) and edit the SDK installer file, removing the dependency on VS2010.
This is how I got the Surface 1 SDK to work with VS2010, since it was targeting VS2008 (note that it still has not been updated to work with VS2010)
Let me know how you go.