tag:blogger.com,1999:blog-1528805174514452404.post8803172223020185401..comments2024-03-27T17:10:25.297-04:00Comments on Allen Conway: VS.NET 2012 Missing Setup and Deployment Project TypeAllen Conwayhttp://www.blogger.com/profile/07010967958393033081noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1528805174514452404.post-39039961523997441752013-05-29T08:34:46.440-04:002013-05-29T08:34:46.440-04:00@Tom - Yes I agree my comments might have been a b...@Tom - Yes I agree my comments might have been a bit harsh about abandoning a project type or even a technology that one has been invested in for many years. From that angle I definitely get it and see your frustration. From what I see, Microsoft is trying not to invest in development components that co-exist in the open source community and dwarf their own functionality. I believe the installer situation was one of those cases.<br /><br />Your comments about Silverlight, Windows 7/8, etc. were spot on and see my other post entitled "Where are we Headed with .NET? It's Anyone's Guess". My recommendation is to tune into the Build conference this year to see how MSFT pulls the development community back together without alienating so many people because of its recent decisions.<br /><br />Allen Conwayhttps://www.blogger.com/profile/07010967958393033081noreply@blogger.comtag:blogger.com,1999:blog-1528805174514452404.post-71435130315050066612013-05-29T04:16:20.544-04:002013-05-29T04:16:20.544-04:00Hey Allen,
You know, we developers out there who ...Hey Allen,<br /><br />You know, we developers out there who are responsible for dozens of real world customer applications, notice such changes in VS 2012 immediately - as soon as we try to port those projects... And migrating all those existing projects generates costs without benefits for the customers.<br /><br />"It's better to become familiar with one of these well known and stable open source deployment products and begin using them anyway."<br /><br />For new projects, yes. I don't know if that's a generation thing, but currently Microsoft is about to completely loose its former strength, which is BACKWARDS COMPATIBILITY. They do it on Windows 8, VS, .NET (Silverlight). The good thing is: Microsoft will remark this in their sales numbers (the only language the top management understands), because business just stops moving forward to the new products. We had this with Vista, now with Windows 8, and VS 2012/AppStore. Will they learn? I don't know...<br /><br />Thanks for the NSIS-hint, will try that one.<br /><br />Cheers,<br />tomTom Fallerhttp://www.comgate.chnoreply@blogger.com