David McAfee
davidmcafee at gmail.com
Mon Dec 13 10:09:41 CST 2010
U use a click once app for our nationwide sales force. Very easy to implement and using webservice calls, seems like a local app. I'll post some samples when I get into the office Sent from my Droid phone. On Dec 13, 2010 7:12 AM, "jwcolby" <jwcolby at colbyconsulting.com> wrote: > > Thanks everyone who has responded. > > Both of these are cases where the company is "virtual" and all the stakeholders are scattered > around. The database has to be accessed over the internet, and from who knows where. > > I thought about trying to do an "application" that just pulled the data from a hosted SQL Server but > then you run into installation issues etc. With "clickonce" deployment even that might be possible. > I think if I could do a real app distributed with ClickOnce I would go that route. It just puts > off learning all of the web / html / java stuff. > > John W. Colby > www.ColbyConsulting.com > > On 12/13/2010 4:45 AM, Mark Breen wrote: > > Hello John, > > > > There are lots of things to consider when you out an app online, security > > being just one. But there are really many other things also, most of which > > I do not know. > > > > However, I am currently happily developing web apps myself, and I spent > > minutes and hours on my coding. > > > > I am using DotNetNuke as my framework and it works a treat. I keep it > > simple and try not to get too fancy. There is loads of help available from > > the groups and forums. > > > > It is not too wild to suggest that in the future 50% or more of our > > customers will want web based front ends, so I urge you to study DNN - a few > > days of reading the forums and the turorials on module development will have > > you coding apps in no time. > > > > Do not be put off by the initial barrier to entry, once you get the hang of > > it, and one you keep it simple, you can code in the same ol' c# style , but > > your GUI will be a DNN website. > > > > Oh, and it if fun also. > > > > Mark > > > > > > On 13 December 2010 06:45, Eric Barro<ebarro at roadrunner.com> wrote: > > > >> John, > >> > >> ASP.NET uses either C# or VB.NET as the underlying development language. > >> Of > >> course there are other technologies involved such as Javascript, HMTL, CSS > >> etc. > >> > >> There's no way to convert a WinForm application to a web app with one click > >> of a button. You'd have to recreate your WinForm in ASP.NET using the > >> built-in .NET equivalent controls. The good thing is that they are one and > >> the same type of control on the web app (ie TextBox in WinForms is still > >> TextBox on a web app). > >> > >> If you programmed your business logic in separate classes and you refrained > >> from directly referencing controls in the methods then you should be fine > >> and you should be able to use most of your code in a web app. > >> > >> The main things you will need to deal with in a web app such as ASP.NETare > >> the following: > >> > >> 1. Session variables - this is one of the ways you can pass data back and > >> forth from one page to the next since web apps are stateless apps and there > >> is no "automatic way" of "remembering" data from one page to the next. > >> 2. Postback events - when a user clicks a button on a WinForm all you need > >> to do is trap for the click event. On a web app you need to be aware of > >> when > >> postbacks (basically trips to the server) occur so that you can properly > >> trap events or intercept them. > >> 3. Server side versus client side events - this is probably the hardest > >> concept to grasp for most beginning web app developers. > >> 4. Client side scripting - When it's done and said, all ASP.NET does > >> really > >> is render the page in HTML and handle the events using Javascript. You will > >> need to get your feet wet learning Javascript as well. Fortunately, the > >> syntax is based on C but variables and objects are not strongly-typed. > >> > >> --Eric > >> > >> -----Original Message----- > >> From: dba-vb-bounces at databaseadvisors.com > >> [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby > >> Sent: Sunday, December 12, 2010 9:33 PM > >> To: VBA > >> Subject: [dba-VB] Browser based database > >> > >> I need to do two different browser based databases (I think). I know > >> nothing about this. Both > >> clients need to enter data and have multiple users hitting the database > >> from > >> home and office computers. > >> > >> Where do I start? I am getting pretty good with C# / SQL Server but those > >> are computer based > >> "applications". If I could do an internet download installation, I could > >> probably (maybe) go there. > >> Except what about admin rights etc. > >> > >> Is asp.net viable? Is it close to C#? If I keep the data entry screens > >> simple can I do it in C# > >> and then just "press a button" to turn it into ASP.net? Please don't make > >> rude noises here. > >> > >> ;) > >> > >> I just know nothing about internet facing application programming and I > >> feel > >> really inadequate on > >> this stuff. > >> > >> -- > >> John W. Colby > >> www.ColbyConsulting.com > >> _______________________________________________ > >> dba-VB mailing list > >> dba-VB at databaseadvisors.com > >> http://databaseadvisors.com/mailman/listinfo/dba-vb > >> http://www.databaseadvisors.com > >> > >> _______________________________________________ > >> dba-VB mailing list > >> dba-VB at databaseadvisors.com > >> http://databaseadvisors.com/mailman/listinfo/dba-vb > >> http://www.databaseadvisors.com > >> > >> > > _______________________________________________ > > dba-VB mailing list > > dba-VB at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/dba-vb > > http://www.databaseadvisors.com > > > > > _______________________________________________ > dba-VB mailing list > dba-VB at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-vb > http://www.databaseadvisors.com >