Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Dec 14, 2012 08:10 PM by jprochazka
Dec 14, 2012 12:55 PM|LINK
Well, i'm studying the possibility to migrate an application that's written in ASP/JScript to ASP.Net (for performance reasons). Since this...:
1. It's true that JScript.net was discontinued in .net framework 1.1 or 2.0?
2. Aside that, there is an way to migrate all ASP/JScript to ASP.Net that's present in .net framework 4.0 without the need to rewrite all the server-side in C# (since i'm allergic to VB)?
3. Do I need to rewrite the database access codes? Or can I use the old fashioned ActiveX objects for a while?
4. Do I really need to rewrite all the server-side code to C#? It's too much code to rewrite... T_T
5. Is there any decent Adobe Dreamweaver plugin to help code ASP.Net pages? The Adobe's ASP.Net plugin simply sucks. And I have no permission to install Visual Studio or any additional software.
Dec 14, 2012 06:54 PM|LINK
1) This is true. http://msdn.microsoft.com/en-us/library/72bd815a
2) Honestly never heard of a tool to do so and if there was one I would think the code would be a mess to deal with. There is a page on MSDN that covers migrating from classic ASP to ASP.NET which can be found here at http://msdn.microsoft.com/en-us/library/dddsc60w which
may help in your transition if you decide to. Keep in mind Classic ASP can run side by side with ASP.NET so you may not have to, depending on the application being converted, change everything at once to ASP.NET but instead convert the project piece by piece.
3) Yes you will but if you are looking to gain performance this would be a huge gain.
4) Afraid so but as stated earlier if you can break apart the current project and convert it piece by piece this might be less painful.
5) I would have a sit down with whoever will not let you install a Visual Studio product and explain that it is the best tool for the job when it comes to ASP.NET. If cost is the issue there is a free express version called Visual Studio Express 2012 for
Web. I have had to fix on more than one occassion SQL injection vulnerabilities introduced by Dreamweavers way of doing things so honestly I do not trust it especially when it comes to allowing it to write code for you.
Dec 14, 2012 07:59 PM|LINK
Well, if i can stick with JScript 10.0 with an earlier version of .Net framework in the web projects, the rewrite proccess is much less painful.
About the problem about not having the permission to install Visual Studio, the place where I'm work, they have the Dreamweaver CS5 license, but not for Visual Studio. And since they doesn't have any budget to pay the VS license only for me (and any buying
proccess IS too burocratic), I have no choice but to stick with the tools wich they gave me.
About the problem I'm facing, I'm mantaining an system written in classic asp/jscript. Their users is complaining about performance. I wrote some optimizations that dropped the response time to 1/8 of it's original time. But that wasn't enough to make the
users stop complaining. Some investigations lead me to one fact: Classic ASP itself is the reason for delay.
But I must say thanks. Your response helped me to make my mind about the migration. Even with Dreamweaver and with the Adobe tools that's given to me and with some courage, the migration proccess is much less painful that I tough.
Dec 14, 2012 08:10 PM|LINK
Heres a link to Visual Web Developer 2005 Express.
Like I said Express versions of Visual Studio are free to use so cost shouldn't be a factor.
You might want to check out the Microsoft WebsiteSparks program as well if things are tight:
There is also BizSparks for start ups if your company qualifies.
And yes Classic ASP, an interpreted language, will always be slower than ASP.NET.
Good luck on your conversion.