tag:blogger.com,1999:blog-5704450.post4977081105932216825..comments2024-03-20T20:27:05.438-07:00Comments on Vishal Joshi's Tangent: 10 + 20 Reasons why you should Create a Web PackageVishal R Joshihttp://www.blogger.com/profile/05217117734084631137noreply@blogger.comBlogger11125tag:blogger.com,1999:blog-5704450.post-59287546910330510562010-09-27T16:48:58.589-07:002010-09-27T16:48:58.589-07:00Ah. Cool.
Thanks, PeterAh. Cool. <br />Thanks, PeterAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-5704450.post-49896148803196454492010-09-27T16:12:57.733-07:002010-09-27T16:12:57.733-07:00Q. It's been over a year now. What's the s...Q. It's been over a year now. What's the secret provider<br />A. I was referring to "runCommand" provider which allows you to run any batch file, which essentially means that you can do anything else which Web Deploy does not support right out of the box...Vishal R Joshihttps://www.blogger.com/profile/05217117734084631137noreply@blogger.comtag:blogger.com,1999:blog-5704450.post-27186704296168631842010-09-27T15:25:55.276-07:002010-09-27T15:25:55.276-07:00Hi Vishal,
It's been over a year now. What...Hi Vishal,<br />It's been over a year now. What's the secret provider?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5704450.post-58046080376451246142010-09-08T08:34:38.658-07:002010-09-08T08:34:38.658-07:00"I do not think you can install web packages ..."I do not think you can install web packages on IIS6. Please check Microsoft website for additional information"<br /><br />Infact you can install web packages on IIS6, you just do not have the inbuilt UI in IIS Manager... You will have to use commandline to install them...<br />-VishalVishal R Joshihttps://www.blogger.com/profile/05217117734084631137noreply@blogger.comtag:blogger.com,1999:blog-5704450.post-38477878360772585922010-09-06T19:37:03.728-07:002010-09-06T19:37:03.728-07:00I do not think you can install web packages on IIS...I do not think you can install web packages on IIS6. Please check Microsoft website for additional informationAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-5704450.post-3816124668215773932009-11-20T01:47:23.029-08:002009-11-20T01:47:23.029-08:00Hi, good article and one close to my heart as I...Hi, good article and one close to my heart as I'm responsible for our organisation's web application deployments. One question: we still use IIS6 here - will I still be able to create and install web packages?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5704450.post-90668750575275267112009-09-10T18:29:59.809-07:002009-09-10T18:29:59.809-07:00Great questions Shane...
Currently the DB Deploym...Great questions Shane... <br />Currently the DB Deployment which comes as part of the packaging experience does not take care of the incremental DB deployment... Although the good news is that DB Deployment allows you to inject SQL Scripts into the package... You can generate the .SQL files either via RedGate or TS Data do some minimum pre processing to them to make them native SQL Scripts and then inject them into the package as part of standard extensibility... I have a work item to document how to do that, which I will hopefully do soon...<br />About ACLs - there is a flag which you can set in your project properties (by manually editing the file) to allow packaging to pick up ACLs from the source box and move them to the destination box... You brought out a great point that the ACLs which are set on your Dev box are different than the deployment server... For this very reason we did not make copying ACLs as part of the UI... For scenarios where ACLs are different due to different domains in dev server vs production/staging it is a very tricky problem... I believe in these cases there will have to be some manual intervention required or there will be additional hooks available which you can use to write custom scripts/exes to do the job... Again I understand it is not straight forward but then the basic MSDeploy model is to replicate source to the destination and your scenarios falls outside the bounds of this model to provide an out of the box solution... But nevertheless it will be possible to do this via extensibility that I will hope to write about sometime soon as well...<br />Thanks<br />VishalVishal R Joshihttps://www.blogger.com/profile/05217117734084631137noreply@blogger.comtag:blogger.com,1999:blog-5704450.post-91850677656855485652009-09-09T10:29:08.820-07:002009-09-09T10:29:08.820-07:00Good evening
What about updates ? How does this ...Good evening<br /><br />What about updates ? How does this cope with SQL Schema changes and existing data for existing web applications.<br /><br />I understand the 'simplicity' for new apps, but how to roll out updates for existing apps ?<br /><br />Also what about security/ACLS, for example each website on our webfarm we run with a dedicated user for that purpose. The application pool runs under that user and the physical directory would then only have read access for that user, unless specific write access is also needed ? For example how to setup tight security on different directories and associated users ? Local dev servers would/could be running in different domains so ACLs cannot just be simply copied across ?<br /><br />Thanks<br /><br />ShaneShane Osbornehttp://www.punkyduck.comnoreply@blogger.comtag:blogger.com,1999:blog-5704450.post-81800183303099572852009-08-10T10:38:28.000-07:002009-08-10T10:38:28.000-07:00Thanks Sheron appreciate the endorsement... Lookin...Thanks Sheron appreciate the endorsement... Looking forward to your feedback as you start playing with the product...<br />-VishalVishal R Joshihttps://www.blogger.com/profile/05217117734084631137noreply@blogger.comtag:blogger.com,1999:blog-5704450.post-10999514500279571922009-08-09T09:52:27.795-07:002009-08-09T09:52:27.795-07:00Wow wow wow...First time I'm reading about web...Wow wow wow...First time I'm reading about web packaging in VS2010...Sounds awesome...<br /><br />This really would solve many of the problems we used to have while deploying to production servers. We developers do not have access to the dedicated deployment servers used by our company (I guess it is a common security practice). And oh man, it really is a pain preparing the documentation explaining how to do the setup and deployment to the server admin guys. Whew and the countless weekends I had to spend in office undoing all the messups made by them.<br /><br />Thanks again guys for making it easier for us...Sheronhttp://spinningtheweb.wordpress.comnoreply@blogger.comtag:blogger.com,1999:blog-5704450.post-52240460472608704782009-07-21T15:20:31.543-07:002009-07-21T15:20:31.543-07:00Looking forward to VS 2010 Web Deployment. Thanks....Looking forward to VS 2010 Web Deployment. Thanks.Anonymousnoreply@blogger.com