3 ms·
One example, if you are using Azure, it makes it very easy to deploy from VS. But again, this is an option and not a requirement. You are fee to deploy however
by codegeek 12y ago
One example, if you are using Azure, it makes it very easy to deploy from VS. But again, this is an option and not a requirement. You are fee to deploy however you please.
- mattmanser 12y agoJust because it's easy, doesn't mean you should. It's a bad habit to get into. Admittedly, there's still no good deploy solution for C# at the moment that isn't a colossal load of work, but web deploy is definitely not a good choice. It's like MS looked at every single choice and went "Hmm, we'll pick the worst of these two options!". Good luck if you need to do a rollback stat.
- sharms 12y agoI will give you a perspective of someone who has used Linux on my main desktop since 1997, but I do keep up to date with other platforms: VS + C# + Azure integration is excellent, and there is nothing which prohibits turning up a 2nd instance any more so than using AWS, Docker, Chef or whatever your choice may be. I am also not convinced Visual Studio is a bad habit, as it has many features and tools which are often superior to open source alternatives (debugging, integration, intellisense). I currently use Vim + Golang and Emacs + Clojure; comparatively those environments do not make me biased enough to say VS does not have some incredible upsides. My assumption is that most people may not have spent enough time with the Windows tools to judge them fairly as we have all been tremendously productive on Linux and there are ideological issues spawned out of the decades of Windows dominance which slant these discussions.
- mattmanser 12y agoWhen did I say anything about not liking VS? You've completely misrepresented what I said.
- waitwaitwhay 12y agoWhats the problem with rollbacks? Just redeploy the package of the previous version?
- mattmanser 12y agoHow long would that take? Is it alright for your site to go down for minutes?
- waitwaitwhay 12y agoI deploy the old version to new virtual machines and reconfigure the loadbalancer to direct traffic to those instances. Or I do a rolling downgrade, one machine at a time and excludes machines being downgraded in the LB. This takes a minute or so (everything is automated) and there is no downtime.