Carl Franklin

I've got plenty of .NET problem stories to tell. Seems like Microsoft didn't really think much about domain controller University environments when creating the documentation for management of .NET.

We have plenty of success stories. I'd love to tell you about how our hybrid Flash/C#/VB6/VC++ portal I worked on for the guys over at Articulate (http://www.articulateglobal.com)is kicking Macromedia Breeze's J2EE arse all over the place at the trade shows, despite the fact that it was/is being developed with a fraction of the resources. But of course, that is only one story... got plenty more :-).

That's EXACTLY what I'm talking about. Let's talk by email.

Yes, I have a great .NET success story. This is a two year old story. We built an application in classic asp. We needed to do something async to the application but did not due to the need to get something up and going. Well because the classic asp application was doing the operation everytime, the app was just two slow. I set down, moved the functionality out of the classic asp application into a .NET Windows Service and the app ran beautifully after that. More specifics are available if you want to talk about it.

Wally

Sounds great. Why not send me the story by email? carl@franklins.net

You've heard from me before, but I'll review our stuff here.

We had no web site when I got here. (1 page does not a web site make.) I started creating forms in ASP classic, but the more we did online, the more we wanted to do.

So, we've developed our site in .Net which integrates orders with Great Plains and our Kodak Production software (SQL database). We used to hire extra help between Sept. and Dec.
Now, not only have we stopped hiring extra help, we've shrunk our staff through atrophy.

We get hundreds of complex orders a day that used to have to be hand entered twice, into Great Plains and the SQL database. Now nobody handles them until it's time to complete the order.

Development staff = 1 (Me)
Training Process = .Net Rocks, Forums, and books