I am working on a ASP.Net project creating a Outlook like calendar scheduler app.
I need to implement javascript on the webpages, but VS 2005 that I am using now is not very helpful, like intellisense or debugging,etc.. in case of javascript. I am planning to use jQuery in the app too.
Questions :
Is there some feature of VS 2005 that helps in javascript, that i dont know, or should I move to VS 2008 (is it better than VS 2005 in this regard?) ?
And also tell me a good IDE to practice javascript, in a HTML-Javascript environment. I am not going to use Rails or PHP or python.
Thanks.
It would be helpful for you to provide details on what sort of "help" you're looking for.
VS2008 has better JavaScript support than VS2005 in general, including JavaScript debugging. Here's a link from Scott Guthrie about VS2008 JavaScript support.
With jQuery, you can add intellisense to Visual Studio to help you out. Here's another link to a post from Scott Guthrie about enabling the intellisense.
I agree that VS 2008 is much better for the environment you are considering, as you can easily add intellisense support for jQuery. VS 2008 can also debug inside it's own webserver or IIS which means that it's very easy to test your environment.
For our projects we use VS 2008 and code using the MVC framework which has incorporated jQuery. I run each web project inside the debug environment before we deploy to IIS for final testing. I use firebug to debug JS in Firefox, Chrome and safari have their own debuggers and VS 2008 handles IE for me.
Another nice feature of VS 2008 is the ability to publish projects to a specific location copying only the required files. I wouldn't want to publish to a live environment but to create the required files within the final testing environment first is a much needed time saver.
Regarding your second question, RubyMine is a great environment for writing JavaScript - great IntelliSense, and it teaches you best practices, too (something that Visual Studio lacks).
It's quite funny that this isn't that much advertised on the product highlights page (it's in brackets, heh)...
Related
Which version of Visual Studio can be used to open a project which is built as ASP Web project
I have Community edition 2019 Does this support ASP projects?
I know these days no one is using ASP for building web apps The purpose is to maintain an existing ASP solution for a couple of more months 9If any bug fix requests from the client comes ) and start to build a new project using the latest version of Microsoft technologies
Visual Studio
Most versions of Visual Studio support editing Classic ASP code, couple of things to keep in mind though.
Frontpage Server Extensions is no longer supported, the best approach is to use a mapped drive or better yet store the code in source control (Git, SVN etc.) and work with the code locally (can bind to a local instance of IIS).
The IDE can be quite cumbersome for working with Classic ASP as it's designed for more modern technologies.
It also has sophisticated debugging through the IDE via the "Attach to process" which will work with Classic ASP running in IIS as long as the web application has been configured correctly for debugging. See How do you debug classic ASP?.
Visual Studio Code
Another option is Visual Studio Code which is a free IDE built on the principle of open source projects for cross-platform. It's becoming a popular free IDE for many developers rivalling the likes of Atom, Sublime etc.
It's lightweight and extensible through extensions, there are already some useful extensions for Classic ASP including this one;
Name: Classic ASP Syntaxes and Snippets
Description: Classic ASP Language Support and Snippets from tmBundle
Publisher: Jintae Joo
It also has built-in support for popular source control solutions like Git and more powerful available through the extension marketplace that is built into the IDE. If you do use Git would recommend installing the GitLens extension.
Every version of visual studio since I started with 2010 (was there something before it?) handles Classic ASP just fine. I'm on VS2019 right now.
I even have a project which is a combo Classic ASP, Webform, and MVC all in one project, with some session sharing, and I routinely code and debug in all. The only limitation is that when you debug, you have to choose whether you're debugging Managed code or "script".
With each I "attach to process" and choose which code I want to debug. Classic ASP debugging is fantastic, and I can't believe more people don't do it. I see basic questions on here which would easily be fixed with standard debugging techniques (settings breakpoints, evaluating variables).
The ONLY thing which isn't supported is code formatting inside <% %> blocks. If I ever get some time maybe I'll make an addon for it.
I need to visualize complex business logic on a single ASP.NET page that has over thousands of lines code so I decided to give Visual Studio's own "Code Map" feature a shot, which is described here: http://msdn.microsoft.com/en-us/library/jj739835.aspx
The tool looks like this:
I tried with VB.NET and C# (including MVC) projects and it was working very well... or that's what I thought, until I tried to use code map tool on an ASP.NET project.
Instead I got this helpful window:
I couldn't find any documentation that says "it's not supported" so I guess I'm doing something wrong? Is there any way to get this tool work, manually trying to add did not help either. I'm open to suggestions.
It appears you're using a File System Web Site Project. These have nebulous support in Visual Studio 2012 and later. I say "nebulous" because I haven't found anything that explicitly states they're deprecated, but the documentation for them is only provided for Visual Studio 2005, 2008 and 2010.
If you need Code Map support for your project, consider converting it to a Web Application.
what is the stack for a asp.net Web forms application?and why?
example for ASP.NET MVC there is an example:
http://codeclimber.net.nz/archive/2009/10/15/my-asp.net-mvc-stack-and-why-i-chosen-it.aspx
thanks
To be perfectly honest, this depends a lot on the specific project you plan to build with WebForms. Since I'm newer to MVC, I do just about all of my .NET development with WebForms. So here's the "stack" (framework + tools + components) that I use when building an application:
Framework
Obviously, ASP.NET WebForms. I make sure to keep all of my different layers (presentation layer - aspx webform, business logic - aspx.vb/aspx.cs codebehind, data access layer - additional classes) separate while I'm building.
Tools
Visual Studio 2010 - I dare you to find a better tool for developing a .NET-based web application.
SQL Management Studio Express - Fantastic tool for managing your database setup
TortoiseSVN - Subversion tool that integrates directly into Windows' contextual file menus. It's great for quickly committing/reverting projects!
BugTracker.NET - Great bug tracking tool that integrates with TortoiseSVN.
Libraries
jQuery - I use this for everything
jQuery UI - Great for adding "squishy" user interface elements and building out more interactive web forms
Flexigrid - I use this for building datagrid elements on my sites. Since it's built with jQuery, it interfaces nicely and handles AJAX data loads remarkably well.
YUI - Another JavaScript library that's great for animations and transitions.
Testing
Visual Studio Debugger - fantastic for stepping through server-side code to make sure things are working
Firebug - Firefox extension - Absolutely essential for debugging client-side scripts and for identifying HTML/CSS errors
IETester - Useful for anyone supporting commercial clients (who might still be using IE6)
For deployment, I use a set of custom tools that create unique filenames for frequently changed files that will need to bypass a user's cache when they're changed - i.e. whenever a CSS or JS file is updated or I change an image, I'll append a unique string to the end of the filename so the browser re-fetches the file.
The stack we have where I work:
Visual Studio 2008 / SQL Server Management Studio Express 2005
Resharper - for helping with coding standards and practices
Subversion - for source control (Formerly had SourceSafe which I had used for years but Subversion is much much better IMO)
Cruise Control .Net - for continuous integration
nUnit/nAnt - for unit tests and automated builds
IIS 5.1 - The downside of still being on XP is that we have these old tools at times.
IIS Admin .Net 1.1 - For helping have multiple sites on one machine.
WatiN - for web-based tests when needed.
In terms of coding add-ons:
jQuery
Sitecore (This is our CMS and is huge in some ways)
Browsers, just to note the big ones here:
IE
Firefox
Chrome
Safari
Tools:
Dev environment -
Visual Studio 2010 Professional - quite an obvious choice given that the latest tool is a big improvement over 2008 edition, especially in terms of performance. There are a few quirks still (waiting for SP1!) but it is mostly a pleasant and productive experience.
SQL Management Studio Express - for DB management
Source control and Project Management - Team Foundation Server 2010 - really going all out with MS here, leveraging our Bizspark membership, TFS 2010 has cool new features including branching/merging, shelfing (vs checking in) and much better transactional integrity than VSS. Also the project management tools are pretty good - there are various templates you can choose depending on whether you want to go Agile, or traditional.
Mantis - for bug tracking, but we are phasing this out and trying to move to TFS. Figuring out how to migrate existing data though.
Libraries:
Asp.net Ajax - pretty cool for what we need, simple ajax effects are quite easy to achieve.
Testing:
MS Test - in built in Visual studio, much better than previous releases - Unit testing support is far better.
Debugging:
Visual Studio Debugger
IE Developer tools
Is it jQuery? Is there a way to integrate support for the excellent ExtJS or YUI libraries?
Any news on whether Visual Studio 2010 will support another JS framework?
I have only seen that Microsoft will support JQuery. But that has less to do with Visual Studio and IIS, and more to do with Microsoft Support practices. JQuery will be shipped with Visual Studio 2010, the Microsoft AJAX Framework, and the ASP.Net MVC Framework (happening now).
But you can use any JavaScript library you want, and if you have the correct service packs you should also get a bit of intelesence with Visual Studio 2008.
The one "extra" JQuery gives you that I have not seen (yet) from other JavaScript libraries is a version of their library with Visual Studio comments in them, giving better intelesense directives.
You can use any javascript framework you like. JQuery comes packaged with .Net, but it's not your only option.
If you have either documented or debug versions of the framework you want to use, VS 2008 will give you IntelliSense of the referenced JS libraries.
If you've installed the additional IntelliSense hotfix KB958502, you can take advantage of VS automatically finding copies of documented JS files named .vsdoc.js or .debug.js next to your referenced minified versions.
Going forward, VS 2010 will have even more support for JavaScript, working out parameter types from usage, etc.
Microsoft have started offering support for jQuery - which is different to VS supporting a JavaScript framework - this means that you can phone MS up and say your site isn't working with jQuery, and they will help you fix it (as a standard support incident, like they would if you found an issue in VS itself, or IIS, or even Word).
yeah you can use any frame work you want, but be careful of frameworks conflict i spent hell of a time to figure out Jquery problems with other framework, until i discovered that it has problem with moo tools regarding syntax, here is the link it will save you hell of a time.
http://groups.google.com/group/jquery-en/browse_thread/thread/3dabd31a8ab60505?pli=1
http://forum.mootools.net/viewtopic.php?pid=26204
Visual studio designer for asp.net applications is generally very slow and i would like to know if there are any tips or guidelines for settings in order to get better.
The problem is usually noticed when i try to make a change in design or source view, especially in source view it may get non-responding for a couple of seconds.
I experienced a very similar issue when I first installed Visual Studio Team System 2008 Development Edition. I have issues with VS design view and could not switch to "Split View"
Reference the following ASP.NET thread link to see if any of this information helps..(Warning: It is quite long).
Do you notice any difference when starting in Safe Mode?
devenv.exe /SafeMode
I assume that you have already installed the hotfix for VS2008 ASP.Net Designer performance issues? Link