Load testing of a classic ASP application in VS 2010 Ultimate - visual-studio-2010

I wish to perform performance testing(load testing) of a legacy(classic) ASP web application, which runs on IIS using VS 2010 Ultimate.
Can you please post the steps.
Thanks in advance.

There is absolutely no difference testing a classic ASP app from any other with VS 2010 Ultimate.
Trawl the Microsoft text on the subject here.
The basic process is to create/record some web tests to hit pages on your site.
Then use the load test to combine these for running against your target site.

Related

Getting error while trying to run a classic ASP website in Visual Studio 2010

I have a classic ASP website deployed over IIS.
I am opening that website from the same location in visual studio 2010 (in order to debug, as per the steps mentioned here
The problem is that, when I hit F5 in visual studio it is giving me an error saying "your server does not support debugging of asp net or atl..."
I am able to browse the site from IIS, but I want to open it in Visual Studio in order to debug it.
What could be the possible reason and solution of this issue?
F5 doesn't do anything good for classic ASP sites (f5 will try to compile a .NET site and then access it).
I will assume that you are trying to debug the site on the same machine where it's running. The way you debug "classic" ASP using Visual Studio.NET is by attaching to the process running the site. The easiest way to do this is to use the Just In Time (JIT) feature: insert a stop statement in the code (debugger in jscript) - hitting that line should initiate a server-side "Error of type "Script Debugging" was encountered. Do you want to debug?" dialog, with suggestions of available debuggers to use.
Try this and report what happens - there might be some extra steps needed to configure that machine.
Are you using IIS 7?
If so you should the server option "Enable server side debugging"... It should be in the properties window of the site, using IIS Management Console.
Once you do that, when you run the server through Visual Studio, it should open another solution on debugging mode with the relevant code.

Load Testing Without Visual Studio 2010 Ultimate?

Is it possible to get the load testing features of VS 2010 Ultimate without buying ultimate? Does MS sell the feature packs a la carte? I'm having a hard time finding a clear answer to this, so hopefully someone here can clarify.
Barring that, but still within the bounds of my question...are there 3rd party load testing tools that are similar to what VS 2010 Ultimate provides?
There are lots of load testing tools available - search for 'load testing software'. I'll pimp our free version: Load Tester LITE.

Reuse Testconfigurations from VS 2008 in VS 2010?

I'm currently investigating my options to run automated tests from within Visual Studio 2008 Professional. I noticed that the MSDN page documenting the integrated funcionality is only available for VS 2008 and VS 2005. This kind of makes me suspcious. Since we are planning to upgrade to VS 2010 I'm wondering whether I will able to continue to use my configurations and knowledge with VS 2010? Does anyone here have made any experience with this?
TIA, Thomas
No need to be nervous, the terminology around the test configuration has merely changed in VS 2010. Most of what you know is the same but resides under different product branding which causes some versioning problems in the documentation.
Most notably, "test configuration" is often referred to as "test settings" under 2010.
Microsoft moved away from silo-ed "Team Test" terminology of VS 2005/2008 to a more holistic big picture known as Microsoft Application Lifetime Management, where testing is an integrated component for delivery of successful applications. Keep in mind that most of the documentation you'll find for testing refers to the Test Manager, which ship with the Ultimate and Test editions of Visual Studio. The Test Manager ties Tests to Use Cases and Requirements and is part of that big picture.
If you're not going down the ALM big picture, the focused view of just running tests hasn't changed much at all, with the exception of some new features like Test Impact which are pretty cool.
The following links may be useful to you, as it sounds like you're interested in how the tests can be used by developers or part of your build process:
Running Automated Tests within Visual Studio
Running Automated Tests from the Command-line
Hope that helps!

What can WebMatrix do that Visual Studio 2010 Ultimate SP1 beta as an IDE can't?

I am seeing a lot of blog posts lately about WebMatrix. I don't read them because I tell myself "I have Visual Studio 2010 Ultimate with SP1 beta". The king of IDE's.
Just in case I am not missing on something important, as an IDE, is there anything that WebMatrix can do that VS 2010 can't do or does better?
Presently:
Access to the Application Gallery which I think is quite a nice feature. I like the way I can grab dasBlog or WordPress, do some edits and miscellaneous fiddling around, test then squirt the app up to the server. I think that's a killer feature for both beginners and experienced devs.
There's also task orientated site starter templates that Visual Studio 2010 lacks
Simplicity - with Visual Studio 2010 there's a lot going on in the UI, all sorts of "technical looking" project types. WebMatrix has one project type which is web projects.
If you have been using VS 2010 or even VWD 2010 and haven't been confused by them so far, you are not missing out on anything. WebMatrix is not intended for you. It has been designed to attract beginner developers, or those who know a little PHP or perhaps classic ASP and would like to try out ASP.NET.
It is primarily designed to make developing Razor Web Pages sites easy, with no clutter. No code complete, no Intellisense (well... except for the wrong kind of HTML Intellisense), no debugging, no compilation required (or possible), no wizards. Bare bones. Knuckle deep in HTML tags and inline code...
Actually, if you are anything like me, you are missing out on a lot of fun ;o)
I am not 100% sure that this is not in VS.net, but one thing I use in Webmatrix is the Reports feature that lets you run an analysis against your site to find common issues with the site like SEO and accessibility. I know this can be done using an IIS7 plugin, but not sure if it can be done directly in VS.net.
The other thing Webmatrix has is a nice interface to IIS Express that allows you to set settings and see requests to your development site in Webmatrix. VS.net 2010 sp 1 has IIS Express support but I haven't seen as nice an interface there.
Also, not too sure if this is not in vs.net, but when you create an SQL CE 4 database in Webmatrix it has a tool to migrate that database to normal sql server.
Finally, something subjective, Webmatrix has a simplicity to it that vs.net does not. VS.net is built for a developer to do anything and everything. It has a gazillion menus and options plus extentions, dockable windows and at least 4 distinct versions. Webmatrix is built just to create web sites. That simplicity lets you go from point A to Z very fast even if you don't know much about setting up web sites, databases or asp.net. It's one IDE where you know that every feature in it is expressly meant for you to create a web site.

will visual studio 2010 support classic asp?

I'm using visual studio 2008 for a classic asp application. Will I be able to upgrade to visual studio 2010?
Yes, classic ASP can be developed just fine in VS2010 as it does in VS2008 SP1.
I've found this msdn page
http://msdn.microsoft.com/en-us/library/ms241740.aspx
it says:
Although the primary focus of Web debugging in Visual Studio 2010 is ASP.NET, you can also debug legacy ASP Web applications.
ASP Web applications consist of scripts, which run on the client in .htm files and on the server in .asp files; the Global.asa file; and .cdf files. Scripts can be in VBScript, JScript, or a mix of VBScript and JScript. They may also be mixed with HTML code and COM objects. You can debug ASP Web applications containing all of these elements.
Right now I'm working on classic asp pages with visual studio 2008 an everything works fine, I can even debug classic asp...
Still couldn't try it with vs 2010, but the page above gives me some hope...
Usually you can manually deploy an asp web site direclty to the inetpub\wwwroot folder (just paste all of your required web page files to the wwwroot directory), where your default.asp page should reside at the root of wwwroot, if that makes any sense.
Then you can create an empty web site with a single project, start your web site by entering http:\localhost in to a new browser window, and you should see your default page displayed.
You can add all of the extermely old asp files to your new fangeled visual studio 2010 application directly from the wwwroot directory.
You should be able to compile your application but you won't be able to debug it at this point.
To debug the ancient application, simply attach to the internet explorer process with the title of your outdated web application (or the wp3p process....), and you will then have debugging functionality.
Or, you can wait for the old yet useful app to throw an error and then use visual studio 2010 as the J.I.T.debugger.
Hope this helps as well.
Happy coding! (if that is possible in classic asp, thank GOD for visual studio)
(-:
To get VS2010 to support .inc files as well as .asp files, see the related question Can Visual Studio 2010 do ".inc" file syntax highlighting?
VS2010 syntax highlighting for .inc files isn't very good even with the Web Form Editor in use; the HTML shows up fine but the VBScript looks like plain text.
I updated my project from VS2008 to VS2010 and everything has been going alright.
In order to get debugging to work with javascript in a script block I have to add a debugger; statement to get it to break. If you have the javascript in a seperate file you can debug with just a break point. The Classic asp will still debug if I attach to the w3wp process.
The javascript intellisense has been working better for me in VS2010 than in VS2008. In VS2008 I had issues with it crashing when I stopped debugging classic ASP. In VS2010 I don't have that problem any more.
Overall I'd say VS2010 does classic ASP development better than VS2008.
For anyone who wants Syntax Highlighting in VS 2010 and can't get it working. I think this works.
Tools>Options>TextEditor>FileExtension
Add the extension ASP and it should be attached to "HTML Editor with Encoding".

Resources