How do I get intellisense for Prototype / Scriptaculous like we get for jQuery in Visual Studio?
It's certainly not perfect, but you can get a little bit by adding
/// <reference path="path/to/prototype.js" />
to the top of your JavaScript files. Actually, if you have a JS file open in Visual Studio and you drag the prototype.js file into your open file, it will automatically add that reference for you.
This will give you very poor IntelliSense support, but perhaps it is better than nothing.
I might be wrong but I really doubt there is any for now.
For now, either you write your own and share with the world or wait for someone to create them.
PS: jQuery intellisense support was released as a hotfix for VS.NET. It makes sense as jQuery is sort of 'endorsed' by the MS guys. Chances for them to release similar support for other JS framework is unlikely I'll say.
Related
I use MVC4 to develop on a website project and installed Mindscape workbench, Sass studio extension.
I also use bootstrap and Jquery script, not sure if this matters.
I usually edit scss file then save changed then view my change in browser while debugging, however, after working for a white, my editor becomes really slow, slow to click button, slow to type ( it takes couple seconds to move cursor ), almost slow at any interaction with keyboard and mouse. I have to restart my Visual Studio every time, it is really painful.
It is obviously something with SCSS extension to cause this slowness, because if I uninstall extension, this slowness is gone with it.
Has anyone also experienced this, and if you find solution of this, please kindly let me know, will really appreciate it!
Two questions:
How can I get JavaScript IntelliSense for ExtJS?
Are there any good tools (e.g. Extensions, NuGet packages) for working with ExtJS in Visual Studio?
Are there any good tools (e.g. Add-on Extensions like FireBug) for working with ExtJS in Firefox?
To use intellisense in VS 2010 you need to reffer which files should be loaded for intelli sense. You can archive this with references in the docs where you want to use intelli sense:
/// <reference path="ScriptFile1.js" />
/// <reference path="Scripts/ScriptFile2.js" />
/// <reference path="../ScriptFile3.js" />
/// <reference path="~/Scripts/ScriptFile4.js" />
for more information on intellisense take a look at the MSDN
For the tools part;
Edit
To Update on highlighting, braces, aso :
Javascript tools is a great package directly by Microsoft
editend
Javasript Parser does a great work for me when writing
For testing & Debugging Firebug is the best you get in my opinion, but you can also use the IE developer tools(install only required for older IE, prior 8 if I am not mistaking) for debugging.
I have found these extensions useful when working with ExtJS in Visual Studio:
Javascript Parser - makes it easy to find functions, shows todo comments
JSLint.VS2010 - code analysis, helps avoid coding mistakes
try this http://www.dxdframework.com/, it's ext 3 integrated with msvs2010, examples are still for msvs2008, but as i know documentation will be updated soon. wiki: http://wiki.dxdframework.com/AllPages.aspx
To answer point #2, I highly recommend Ext.Net for working with ExtJS in Visual Studio, assuming you are using ASP.NET.
Best resources for wiring up IntelliSense for EXTJS in VS 2010+ is here:
http://gurustop.net/blog/2012/03/03/javascript-js-intellisense-auto_complete-in-visual-studio-11-beta-the-web-_references-js-file/
Note the "Updated" comment at the bottom:
"...you can add files to the global JavaScript intellisense from the Visual Studio Tools –> Options Dialog."
This worked for me after I added "ext-all-debug-w-comments.js" to the list and turned off Resharper's IntelliSense for JS files only.
Just wanted to know that how good is the Visual Studio 2010 for designing UI wireframe?
Is there any major shortcoming in VS2010 in this area.
The UI that i am going to create are the mock up UI but i intend to use the same in future for actual web application development.
Please help, as i am going to use it for the above mention work .
I would rather use visio or any other Mockup tool, see here: http://webdesignledger.com/inspiration/18-great-examples-of-sketched-ui-wireframes-and-mockups
I don't think Visual Studio alone without any AddIn would be very useful in this.
If you want a microsoft product why not use sketchflow http://www.microsoft.com/expression/products/Sketchflow_Overview.aspx
AS you may already have blend installed.
I've started using the Balsamiq mock-up tool for quick prototypes, it's good for that early mock-screen stage but it might be too simple for what you want.
http://balsamiq.com/
There is a web-demo you can try, my favourite feature about it is that it doesn't look like a finished product so it keeps things looking suitably "prototypey". I've tried sketchflow after watching the incredible demo video but it was much buggier and unreliable when I tried it for myself and I spent more time fighting with it than I did coding so I just ditched it and went back to the Balsamiq tool.
Wondering if anyone knows if the feature to allow add-in's for Visual Studio 2010 xml comment viewer was cut in the final release?? What I am talking about specifically is this:
I took this image from this page on MSDN (http://msdn.microsoft.com/en-us/magazine/dd722812.aspx) I can't seem to find even one addin with this functionality, anyone know?
Thanks,
Jeff Lundstrom
It was a prototype someone built, not intended to ship. As it stands, some people internally have played around with it, though still not with the intent of shipping it anytime soon. Sorry :(
(It could be written as an extension, as the prototype was, but I'm also not aware of anyone else, internal or external, who has).
I am having problem in using the source view of an asp.net page in VS.net 2008 IDE. I am not using Design view at all. IDE hangs a bit every now and then, when I use intellisense in it, and I scroll the page.
Please throw some light on it.
Such issues doesnt come up while editing the HTML page, and while editing same asp.net page with the HTML editor which can be configured using Tools -> Options menu option.
Read this Post
This might help to make your visual studio a bit faster in general. I am not very sure about the exact reason for the behavior you mentioned of your Visual Studio.
I suspect that it has something to do with Graphical Interfaces like Toolbox etc.
Thanks
I've had problems like that with Visual Studio before. The intensity of the problems seem to multiply exponentially as the size of the file I work with gets larger.
Here's what I'd reccomend:
Check and make sure Visual Studio is fully updated (Help > Check For Updates) ; there have been some patches released and they will help you immensly!
If your code has any breakpoints, disable them all and start afresh later (Debug > Disable All Breakpoints)
If that fails, here are some more optimizations you can try.
In my case, I think longer file is the culprit. I think partial page concept should be applicable to asp.net page too.