tag:blogger.com,1999:blog-9537945.post8241237801008565062..comments2023-08-20T04:16:39.520-05:00Comments on Deployment Engineering Archive: Deployment AntiPatternsChristopher Painterhttp://www.blogger.com/profile/12167478740431444267noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-9537945.post-1376741218025889832012-06-28T14:21:14.351-05:002012-06-28T14:21:14.351-05:00Based on your paraphrasing, I don't think you ...Based on your paraphrasing, I don't think you understood what I was saying at all.<br /><br />I didn't say an in house application wasn't a "real" application, I was saying it's not a "product".<br /><br />When I say "product" I'm talking about something that is fully shrinkwrapped and sold on the open market. Think Sharepoint or Team Foundation Christopher Painterhttps://www.blogger.com/profile/12167478740431444267noreply@blogger.comtag:blogger.com,1999:blog-9537945.post-9739705366833094432012-06-28T13:35:16.173-05:002012-06-28T13:35:16.173-05:00It's rather unfair to say that "if you do...It's rather unfair to say that "if you don't deploy to multiple customers, you don't have a "real" application". <br /><br />The webdeployment project and web.config replacement works excellently for web projects, and the same process can be applied to .net apps. <br /><br />Yes, his example uses Visual Studio. It is better to use something like CC.Net so that Anonymousnoreply@blogger.com