So I found a pretty cool article out using a “Whidbey like” method of doing Master pages with the .NET Framework 1.1 (Simplify Site Updates with Templates). At work, I tried the code out and thought it was pretty interesting. So I thought I would give it a go on my test computer at home, but of course I had issues.
This post moved to: http://agramont.net/blogs/conrad/archive/2006/02/28/16.aspx
A few weeks ago there was some content updates on ms.com/serviceproviders. During that “refresh” the URL to the Web Admin Tool was changed. I only knew about this after several emails, WAT community posts, and comments on my blog. It's still pretty cool to see people so interested in a tool I wrote almost 3+ years ago.
You know, I often wonder if I should try to build another UI that does the same thing as WAT, but using ASP.NET and MPS as core components. I guess I never really tried because I often thought others would build such a thing. But then again, I thought the same thing before I built the Web Admin Tool the first time around.
Here is a pointer to the Web Admin Tool: http://www.microsoft.com/serviceproviders/webhosting/webadmin_overview.asp
- Conrad Agramont (firstname.lastname@example.org or email@example.com)
For those that would like to comment on me building a new UI (WAT 2.0 or something) ...
- Should it require MPS or use MPS as an option (if MPS is an option, is it cool that transaction support is not provided?)?
- Should it focus more, less, or equal on Service Providers vs. Enterprise needs?
- Would you be willing to pay ($$$)? (The answer to this helps me (conrad agramont) whether to go through the trouble) If so, how much (you can email me with the answer if you want :) )
- Is it better to provide the entire source and charge more or close the source and charge far less.