And we are not talking about meeting your political family, or that moment of hesitation before writing the first test of a class. I am talking about deployment to a whole new different environment. I am talking about the pressure of the client to show everyone and their cat why they had spent so much money to replace an existing working system. I am talking about deployment to the live environment.
After a long silence... here we go again!!
And what better to come back than with a nice-long history?
We have this Commerce Server Site that uses Moss as it's content manager. We will have (someday) content-only pages, but for now, we have data-driven catalog pages. They are still Moss pages, that contain web parts that display catalog information based on what there is in the url.
Wow, I am in the need to rant against Moss. That's how ungrateful I am.
I do not think I am asking too much of one of the flagship products from Microsoft. A product that it's meant to be (amongst 1500 other things -I feel pity for the guys writing the features document for Moss-) the web content management solution (once CMS is defunct) offer from Microsoft. Note that we are not talking about a 3-odd employee shop somewhere in a remote country serving solution for local clients doing some niche activity.
This one is really, really, weird.
We use virtual machines in my current project for developers workstations. Those VM contains (amongst other software) Moss, as this current is about Moss (not really but it used it).