|
Well put, MatrixDud !
Now if only what you said had been part of a course in high school, my app would have been in the cloud long ago!
But I went down another road and now, I've got this huge pile of (cool) code to push around into other smaller piles, I guess. 
Thanks for taking the time to share your very relevant perspective to this discussion!
Bob
____________________________________________________________________________________
The Vulcan Science Directorate has determined that time travel is impossible.
|
|
|
|
|
Correct me if I am wrong, but it seems to me that web applications are mainly for publishing type of applications. In other words, if your desktop applications involve a lot of user interactions, then they may not be suitable for the web. Otherwise, it is not too bad to port them using either of the current available technologies.
|
|
|
|
|
Cloud computing or SAS proponents would say the opposite. Salesforce.com would be considered very user interactive.
|
|
|
|
|
George from Saanichton wrote: web applications are mainly for publishing type of applications
My feel for this is that, like it or not, things are generally moving to the cloud (the web). Whether that ends up benefiting humanity is another question. I'm quite cynical about the whole thing. But it's not so much what kind of app is suitable for moving to the cloud. In my mind it's about the IT people in an org. They want to adopt applications for their org that can be supported centrally, not on every user's desktop. So the browser is the ideal desktop app - it is conceptually a window into the cloud, where the real app resides, and needs no updating. When there's a version update, the app vendor (me) just sends them an update to the app on one of their servers. The user receives the benefit of that the next time they launch the app using their browser. There are other benefits (and drawbacks) too, and CodeProject and many other sites are full of those discussions I'm sure.
Thanks for taking the time to share your thoughts on this!
____________________________________________________________________________________
The Vulcan Science Directorate has determined that time travel is impossible.
|
|
|
|
|
I've done a lot of work in both web and desktop; mostly web though. I would seriously consider why you want to make this change. If you've made it 10 years, then I'm guessing it's not something that is urgent or needed. Sounds like more of a nice-to-have right? However, if web is truly something needed, then ignore my post 
We all know the benefit of why people choose to write an app as a web app instead of a desktop app. But, what people often underestimate is the benefit of why people would choose to write an app as a desktop over a web app. Two HUGE things come to mind. First, is the responsiveness of the app. A desktop app will always be more responsive than a web app regardless of what some web zealots say. The other is the rich environment a desktop offers. The web is catching up here, but IMO still isn't as fully featured as a desktop app. Especially when you get into 3rd party controls like Infragistics... In fact, there's several internal apps at my work that are web apps that are SUCH a pain to use simply because they run in a browser. If they were just done as desktop apps, it would be so much better. On a side rant, with the improvements of RDP and VPN, I think making intranets apps web based is less important these days...
If you feel like you need web, then I would consider what one of the posters suggested. That as, just start with small bits of your app as web.
|
|
|
|
|
|
Bindows!
Interesting!
Thanks, squeek, I will study that.
____________________________________________________________________________________
The Vulcan Science Directorate has determined that time travel is impossible.
|
|
|
|
|
Have a look at the MVVM pattern that is in common use in WPF coding. It's basic selling point is that it completely separates the UI from the business logic. You could re-code separate pieces of the app over time, with no change on the UI. This would allow your users to act as a last line of defense against UI-breakage ("Hey, after the last update, XYZ broke"). Then, when you're finished with this separation, your Web UI will be a mechanical process of coding UI's for each piece.
You said that the app is multithreaded. Does that imply that it is computationally intensive? All business logic will be centralized so your server will have to be beefy enough to deal with it.
Before .NET 4.0,
object Universe = NULL;
|
|
|
|
|
You have already received lot of nice replies. I hope mine too adds something. BTW I am a windows forms fan so I would avoid doing this.
1. Your application must be divided in to layers I suppose. So reuse existing code after refactoring.
2. Do not try and achieve similar experience in UI as in windows application. It will be tough to give similar experience.
3. If it is related to some business process, have a look into work flow as well.
4. Do not forget to rewrite what deserves to be rewritten.
5. You can use use WCF but do not think of replacing remoting with that, try and make it SOA compliant for in future, you do not need to worry much.
|
|
|
|
|
Thanks very much d@nish!
d@nish wrote: You can use use WCF but do not think of replacing remoting with that
It sounds like you have had a problem that leads you to this conclusion, am I right? My app is heavily using remoting. I was under the impression that WCF was supposed to do everything remoting does. Also, could you please expand the acronym, SOA, I'm not familiar with that.
When you mention "work flow", I assume you mean using visio or similar.
Again, thanks for taking the time to provide such a thorough reply.
____________________________________________________________________________________
The Vulcan Science Directorate has determined that time travel is impossible.
|
|
|
|
|
Sorry for the late reply.
BobishKindaGuy wrote: It sounds like you have had a problem that leads you to this conclusion, am I right?
No. All I am saying it do not restrict it to remoting. If you rewrite things as a web service, your application will become network independent. You can then very well use it with clients in other technology as well.
BobishKindaGuy wrote: Also, could you please expand the acronym, SOA, I'm not familiar with that.
It is Service Oriented Architecture. Maybe a quick read on MSDN would help understanding.
BobishKindaGuy wrote: When you mention "work flow", I assume you mean using visio or similar.
With .Net 3.0 and above, we have Workflow Foundation. It suites if your application deals in business processes. Something like leave approvals where you have a series of dependent activities happening with human interventions here and there.
|
|
|
|
|
Thanks again, d@nish,
I have considered a webservice in the past, but to create a responsive interactive experience such as is possible with two-way remoting, would be difficult with a webservice, since the client would be "pinging" the webservice way too often. Or maybe others have achieved that... It certainly would simplify things though. Thanks for the clarifications on SOA and workflow foundation. I'll look into that.
____________________________________________________________________________________
The Vulcan Science Directorate has determined that time travel is impossible.
|
|
|
|
|
I don't know much about your application nor will i read all those replies to see if my answer is already said,
but my answer would be a simple solution to work in between, you will have to write no code at all nor using any plugins to convert your solution, all you have to do is getting a server "PC with windows server will be enough" and a static IP and a webgate certificate from microsoft
then implement the TS service and webgate "Terminal services" then people can run your application from your website as a winform application on remote desktop, I tried this option with many of my applications and it worked like charm
|
|
|
|
|
Thanks very much, nazmolla,
Sounds interesting!
I have customers who have a workstation at work, and may also want to work from home. How do you see this implementation working for them?
____________________________________________________________________________________
The Vulcan Science Directorate has determined that time travel is impossible.
|
|
|
|
|
Thanks for your interest,
for your customers the solution sure will work but you have to take into consideration the cost of the server and the TS webgate certificates, so if they only want to access their own workstations there are a couple more solutions they can do including using the teamviewer,
anyway you can try it without paying anything first by downloading a trial version of windows server 2008 R2 and implement the TS service and apply a temp certificate for free
and if it worked as you like then buy it
you can find detailed info about TS and remoteapp and their step by step implementation here
http://technet.microsoft.com/en-us/library/cc753844(WS.10).aspx[^]
|
|
|
|
|
Thanks,nazmolla.
Your suggestion is very useful, since it shows a way to work with the existing desktop application rather than rewriting it for the web.
This is not the direction I wanted to explore in the original question, but of course, sometimes we need to look at the bigger picture to evaluate what is the best direction.
____________________________________________________________________________________
The Vulcan Science Directorate has determined that time travel is impossible.
|
|
|
|
|
You are most welcome, actually i till a month ago didn't even know about the TS and remoteapp till our VPN connection went down and our ERP stopped working "Microsoft Ax dynamics 2009" then someone at our ISP made this suggestion instead of us buying a new webportal module or an DIA connection with around a thousand dollars monthly to implement the TS for free, and when i read more i found it very useful and now i actually stopped all other VPN connections to our branches and started using this solution,
anyway, you are welcome and i am ready to help you if you needed anymore assistance with this regard
|
|
|
|
|
My thoughts, if you find them useful.
While the technical aspects are important, you also need to consider the business aspects. In general people pay less for things over the web, but you probably have access to more potential customers. So it depends on your market size, how large is your current customer base and does it have the potential to grow larger by going web.
If your market is a niche then it may be lttle point.
WinForms to Silverlight Experience
====================================
We have an airplane flight mapping WinForms app and have done a basic silverlight version. What we have learnt is that Bing maps can't handle the sheer number of points we would like to draw, so we often go into some kind of compromise, less frame per second etc. This is just an example of the broader point that for graphics intensive apps the desktop is a better performer.
The other thing we noticed is that it was much easier to make a series of silverlight app as seperate web pages to do only one or two functions from our WinForm app. When we tried to combine many functions together into one silverlight page then little things started happening like the datagrids started slowing down when scrolling. I think this was due to a few reasons, unoptimised code, inexperience with Xaml, extra code complexity, lack of maturity of silverlight tools and controls.
We still code in vs2008 and its xaml parsing is terrible,badly formed xaml can be hard to find. I assume its got better in vs2010, but i have heard bad reports of vs2010 and i await a service pack.
If you think it it going to take you 1 year to migrate then silverlight will be mature by then i would suspect. I have seen the silverlight related products mature even in the 12 motnhs we have used it.
If you do go the silverlight path I would choose one aspect of your app and move it first to silverlight as a test case. We are happy with the final result as the UI is much easier to use than our WinForms app and has all the deployment and update benefits you get from a web app.
|
|
|
|
|
Thanks, Tim! I do find your comments very useful, and I appreciate you taking the time to document your experiences with SL versus a desktop app. Others have mentioned SL as a way to go, and I am beginning to think that might be a big part of the answer.
I love your suggestion about using several smaller SL apps to get various bits of info for a page rather than one big fetch.
From what I've seen on myVBProf.com, Bill Burrows demonstrates that VS2010 is much improved for xaml stuff.
____________________________________________________________________________________
The Vulcan Science Directorate has determined that time travel is impossible.
|
|
|
|
|
I am doing that with an application as we speak. It will take awhile. Web applications architecture is completely different. If your application is millions of lines of code and it took you 10 years to develop it will take you at-least that to convert it to a web application - if you can duplicate all of the functionality to start with.
Web development is cool, but very work-intensive. It's not WYSIWYG in the same way a Windows application is.
You're not talking conversion here, you're talking complete rewrite. Completely different programming model.
-Max
|
|
|
|
|
If you have a sound database think about using one of the good code generation tools. there are several good ones out there and will deliver professional looking sites with decent security models and n tier architectures. What ever you spend on a good tool will recoup it selve in learning and development times eg std code models the things like ajax several of the tools also have wyswig design features and work with visual studio and no propreitory coding or licensing.
I use Ironspeed enterprise editon www.ironspeed.com but there are several others check out things like lightspeed for another option
http://www.mindscape.co.nz/
You only have do add your proprietory logic which is usually a small proportion of your code. The major part is learning how to get the best out of the tools and all the options offered within It pays to down loat the demos and play and read the help the full versions are really powerful for the average developer needing to get a job done.
Gerard
Gerry
|
|
|
|
|
Thanks Gerard!
Yes, good suggestion to consider the code gen tools.
Your point about the business logic being smaller than all the plumbing code is very true.
If my attempts at following OO practices have been successful, it may be that I can pull the business logic out and replace the plumbing code with a tool. I'll consider that suggestion. Thanks for taking the time to share your experience with the community!
Bob
____________________________________________________________________________________
The Vulcan Science Directorate has determined that time travel is impossible.
|
|
|
|
|
Evaluate Silverlight (V4). Might meet your requirements.
|
|
|
|
|
Thanks kofflerd,
I am beginning to think you are right.
____________________________________________________________________________________
The Vulcan Science Directorate has determined that time travel is impossible.
|
|
|
|
|
if you think this is the direction you want to go this could be your development enviroment
Silverlight 4
Entity Framework (Model)
RIA/WCF enabled entities
MVVM Pattern
MVVM Light Toolkit
Managed Extensibility Framework (MEF)
Silverlight Toolkit
Telerik Silverlight Controls (if more powerfull controls are needed)
Visual Studio 2010
Expression Blend 4
Maybe the "out-of-browser" functionality could be interesting in your scenario also.
Daniel
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
