Using WTL in commercial applications
-
Yep. I'm an senior developer leading a team that's writing a ATL & WTL-based product for the gov't. (OK, not really commercial, but definitely not in-house.) We're about to enter our beta testing in a few months. I know that Gen (by DevelopMentor) uses WTL as well.
-
Hi, I was wondering exactly same question a few weeks ago and I've got below answer from MSFT. ---------------------------------------------------------------------------------------- WTL is perfectly reasonable to use in a 'real' product. The Movie Maker application in Windows ME is written with WTL. There are other pieces of Windows XP that use WTL and probably stuff I'm not familiar with. It depends on the amount of maintenance you (or your company) want to take on yourself. If you want SP's, support from PSS, compatibility in future versions of VC, that kind of thing, then WTL probably isn't a good choice. There are plenty of people to help answer questions on codeproject.com, WTL mailing list on yahoogroups.com and other places. So if you're willing to consider WTL just part of your own codebase then the likelihood that you'll get completely stuck on a problem you can't solve seems reasonably low. Walter Sullivan Lead Program Manager, ATL/MFC -------------------------------------------------------------------------------- Hope this helps. Regards, Ryan:cool:
-
We are just about to start using WTL in a printer driver. Its all coded and working, it just needs to go through testing. It was even demoed to high level management at two other companies (the functionality that we coded that used the WTL) and there was no problems with it. The next applications that my group is releasing by end of year will also be WTL-based. On the side, I use WTL in my shareware that I develop at home. Much nicer than making sure what version of MFC DLLs are installed or compiling statically. Steve Maier, MCSD
-
Hi, I was wondering exactly same question a few weeks ago and I've got below answer from MSFT. ---------------------------------------------------------------------------------------- WTL is perfectly reasonable to use in a 'real' product. The Movie Maker application in Windows ME is written with WTL. There are other pieces of Windows XP that use WTL and probably stuff I'm not familiar with. It depends on the amount of maintenance you (or your company) want to take on yourself. If you want SP's, support from PSS, compatibility in future versions of VC, that kind of thing, then WTL probably isn't a good choice. There are plenty of people to help answer questions on codeproject.com, WTL mailing list on yahoogroups.com and other places. So if you're willing to consider WTL just part of your own codebase then the likelihood that you'll get completely stuck on a problem you can't solve seems reasonably low. Walter Sullivan Lead Program Manager, ATL/MFC -------------------------------------------------------------------------------- Hope this helps. Regards, Ryan:cool:
If you're asking the question not just from curiosity, but to actually get a feel for the feasibility of WTL for your own app, then I suggest looking at the thread "Using WTL for full-featured desktop app" on the Yahoo! Groups list. groups.yahoo.com/group/wtl Several people responded to that thread with their thoughts and recommendations. I agree with Walter Sullivan by the way ... I've had no problems with WTL 3.1 during my development, and the WTL group is very responsive. You just have to be ready to delve into the source code.
-
If you're asking the question not just from curiosity, but to actually get a feel for the feasibility of WTL for your own app, then I suggest looking at the thread "Using WTL for full-featured desktop app" on the Yahoo! Groups list. groups.yahoo.com/group/wtl Several people responded to that thread with their thoughts and recommendations. I agree with Walter Sullivan by the way ... I've had no problems with WTL 3.1 during my development, and the WTL group is very responsive. You just have to be ready to delve into the source code.
-
I have been using it for the last few months, here and there in various small COM objects. I had to port an MFC Application to an ATL COM Object and the controls classes saved me loads of time for porting dialogs. If you are an MFC developer using ATL I highly recommend them. My company's first shrink wrapped full application using WTL will likely be out the door in a couple of weeks. It seems to be working fine. Should I find anything in the WTL that doesn't work, I'll likely just go to the Win32 API to get the job done. "There's a fine line between clever and stupid" - David St. Hubbins