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.
Related
I'm writing a program in C using Visual Studio 2010, and I am getting the following error:
U1095: expanded command line '(here come includes-includes-includes)'.
Some of my colleagues get the same error while others do not. The only easy feasible solution I've tried is to update NMAKE itself from a shady website (NMAKE is very hard to find).
Erasing include entries helps, but eventually we hit the limit again. One hack that works is to use all the includes in a single file per Microsoft's offering and read from that file but I'd prefer to not have to do that.
Is there an official way to update nmake without installing the Windows SDK or Visual Studio 2015?
I would not recommend using anything in programming in general that you "downloaded from a shady source". That sounds like a good way to embed viruses in your shipped code unknowingly. There is no nmake standalone, so you will be forced to use the one that ships with Visual Studio.
Some things you could try:
Attempt using 32-bit and 64-bit versions of nmake and see if you get different results.
Get a more recent version of Visual Studio and see if it works better there.
Thanks a lot for your responses, guys.
Manipulations with nmake didn't help at all.
The answer is: to completely erase a sandbox and get a clean one. So it wasn't MS-VS-2010 problem standalone, but a combination of problems between MS-VS and MKS/PTC Integrity.
I've recently had the misfortune of being upgraded to Visual Studio 2013 at work and it has been nothing short of a nightmare. Ever since upgrading my large scale WPF application to .NET 4.5.1 in Visual Studio 2013, I've been getting mysterious 'fake' errors appearing in the Error List. Sometimes they even stay after a Clean and/or Rebuild, but they not really true errors. Here is an example where you can see that I have just cleaned, but still the errors remain:
I want to be clear here... there is no problem with this view model and I can build that project, or the whole solution without (real) error and the application also runs perfectly:
Furthermore, when running the application there is also a problem that it has with image paths. My images are all displayed perfectly, but I get these 'fake' errors again:
Note that the listed paths are even displayed incorrectly:
C:\Midas;component\Images\Actions\Delete.ico
In the UI, it is referenced like this:
<Image Source="/Midas;component/Images/Actions/Delete.ico" ... />
I'm not really sure whether these fake errors are caused by changes made to Visual Studio 2013, or by changes made to the .NET Framework in versions 4.5, or 4.5.1. I'm hoping someone can shed some light on this for me, because I'm about ready to downgrade to .NET 4.5, just so I can use Visual Studio 2012 instead.
It looks like you're using the /{Assembly};{path/to/Image} construct without the pack:// uri prefix. The editor is warning you that it can't find the file because it doesn't really understand the Uri (until the application is actually built). It'll be defaulting to looking on the file system and trying to prefix it with file://, which of course results in a relative uri to the working directory of the Visual Studio process.
I suspect that if you explicitly include the pack:// uri prefix, that the editor will stop complaining.
pack://application:,,,/Midas;component/Images/Actions/Delete.ico
That way the designer will just know that it should not be trying to look for a file:// location.
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.
We are using Visual Studio 2008 to develop a winforms application stored in Visual Source Safe 2005.
If one of our team members changes a *.Designer.cs file without changing the form's source file the change doesn't appear during a "Get" operation. However, if in Visual Studio you run a compare on the *.Designer.cs file the differences are displayed in the difference viewer.
FYI: We are using the default Microsoft Visual SourceSafe plug in for Visual Studio.
Any ideas why the "Get" operation will not detect changes in the *.Designer.cs files and suggest we pull down the latest version?
Thanks for your help!
Designer files are not intended for manual manipulation. One of the chief incentives for adding partial classes to the popular .Net languages was to segregate the designer-generated code from manual user code, in fact. Manual manipulation of repeatedly-generated code (in pretty much any environment, not just visual studio) is asking for headaches.
What changes are you making to the designer file, and why is it not possible to make those changes to the non-designer source file?
Edit:
Is the project in the IDE properly bound and connected to the source control database (via File->Source Control->Change Source Control)? It should automatically be checking out the designer files when changes are made in the designer view.
I would try doing a Get manually through VSS Explorer (i.e. not through Visual Studio) and see if it works. If not, check to see if the file is pinned to a previous version.
Woe unto you for having to use SourceSafe. At my last job, we used SourceSafe and had a myriad of problems with it. We switched over to Surround SCM and were really happy with it. I'd never heard of it before that job.
To answer your question, any time I ran into a problem like this with SS, I'd do a "forced get": in the options dialog when you get latest, tell SourceSafe to get the latest version from the server regardless of whether it thinks the file is up to date.
Edit: I think the issue is the VS200X plugin for VSS. If you have the VSS standalone application you should be able to do a forced get from there. I now remember having to do this so often that I stopped using the VS200X plugin.
It seems that Microsoft wants Silverlight to take off, yet I cannot find an easy way to develop in it without buying Visual Studio 2008. Has anyone out there found a way to get the silverlight development environment in the express editions of Visual Studio? Any other tools?
Here is a link for ya: HOWTO: Silverlight and Visual Studio Express,
I haven't tried it myself though.
They just released Eclipse tools for Silverlight (eclipse4SL) and I remembered this thread!
Apparently express support will come with the final release
Depending on what you consider "productive", you could work with XAMLPad for a lot of the basic declarative stuff.
The Moonlight project is working on an IDE called Lunar Eclipse, that I think they're eventually going to be integrating into MonoDevelop. Wikipedia says it's in the SVN repository already, but I don't know if there's any code for that which can actually be run effectively yet. I'd think if it's out there it'd be unusably basic if it even compiles... still, something to look into!
I only use Visual Studio as a text editor for xaml and C#. I don't use the designer in Visual Studio at all. You can put together most of your UI with Blend, open your C# files individually with Express. You don't have much intelisense in Visual Studio for the xaml anyway.
As #Brian stated, you can just use Expression blend and create any WPF/Silverlight apps. Especially if you have some Flash background/more interested in the interaction design (UX) I would recommend you to buy expression blend than VS2008.
You can write C# code in notepad and Blend will take care of the compilation.