| .NET integration - windows app + asp app Hi guys,
I know .NET is a bit controversial at the moment on this board, but I'm in a dilemma for a project I'm trying to wrap up by Thursday and would appreciate any bright ideas. I have a regular windows app made - VB.NET with several forms, and I'm trying to figure out how to go about deploying it as a web application, as an ASP.NET - can it be done in a simple manner? Ideally, I'd like to setup the ASP pages and migrate the windows app on to the ASP form - can that be done or am I just dreaming here? Or will I just have to start from scratch on the ASP page?
Thanks in advance!
--
-FF |
|
 PetePumaHow many lumps do you wantPremium,MVM
join:2002-06-13
Arlington, VA | They're really different things with different event models. They are both easy to write, but the idea of the same code for both thick and thin client is pretty much a pipe dream.
Not that you shouldn't be able to reuse a lot of the business logic, but you'll want to start fairly cleanly with regards to the presentation to do it right. |
|
Reviews:
 ·AT&T U-Verse
| reply to FalconFlyerx
If it was properly developed then it should be fairly easy to convert. You can't just turn it into a web app, but with a bit of luck you can reuse most of the code and just wrap it into a new interface.
And .NET isn't controversial, some people just don't stand the idea that M$ is doing good things and vi isn't exactly an IDE  |
|
| reply to FalconFlyerx
Thanks to both of you for chiming - pretty much what I thought too.
--
-FF |
|
 fcislerPremium
join:2004-06-14
Riverhead, NY | Here's another option you could possibly consider:
Click Once
It's very dependent upon multiple things, though. |
|
|
|
Reviews:
·AT&T U-Verse
| said by fcisler:Here's another option you could possibly consider: Click OnceIt's very dependent upon multiple things, though. That has nothing to do with OP's issue. |
|
fcislerPremium
join:2004-06-14
Riverhead, NY | And how so?
From what I gathered, he basically wants to take the application and "move" it ASP.NET.
Let's say what he wants to accomplish is having the application available from outside without having an install - then it does have something to do with his issue. Hence the "It's very dependent upon multiple things."
I also didn't ask what version of VS. What about a WPF application? Does that have nothing to do with his question?
There's more than one way to skin a cat, as they say, and I listed another method. |
|
Reviews:
·AT&T U-Verse
| reply to FalconFlyerx
His requirements were very clear:
quote:
I have a regular windows app made - VB.NET with several forms, and I'm trying to figure out how to go about deploying it as a web application, as an ASP.NET
You just can't transform a Windows app into a web-based app with a deployment tool. You can make a package for installing from a webserver, but that's a totally different thing.
A web-based app is an app where the code (or most of it) is executed on the server, while the browser acts as a GUI. Some components available for Windows-based apps just don't exist as web components (ex NotifyIcon). |
|
fcislerPremium
join:2004-06-14
Riverhead, NY | I absolutely hate this phrase - think outside of the box.
I proposed a solution which COULD WORK. Again - it depends heavily upon his criteria and needs. It's NOT going to work as making it a "web application" - but if he just wants to be able to go to a webpage and "use" his application, it can work.
I never said transform - how about "utilize in a different way".
It was a perfectly valid idea. It may or may not work for his needs. If you don't see how then that's fine, but don't tell me that it's not a valid idea or applicable to his solution. |
|
 SeandhiSeeing From a New LevelPremium
join:2003-04-19
Humble, TX | said by fcisler:I absolutely hate this phrase - think outside of the box. I proposed a solution which COULD WORK. Again - it depends heavily upon his criteria and needs. It's NOT going to work as making it a "web application" - but if he just wants to be able to go to a webpage and "use" his application, it can work. I never said transform - how about "utilize in a different way". It was a perfectly valid idea. It may or may not work for his needs. If you don't see how then that's fine, but don't tell me that it's not a valid idea or applicable to his solution. It would really depend on the requirements of his application. ClickOnce is great for deploying applications because you can publish updates without having to go through a whole install process every time you make a change. However, its limitations include not being cross-platform (if his requirement is that it runs on mobile platforms, Mac, etc. this would not work) and not being a true thin client solution.
--
You're an enlightened cat, and I dig that. |
|
