News for hackers. Stuff that matters.
Re:Visual Studio 2013 released to web by Pxtl on Thursday October 17, 2013 @08:12AM (#6564818)
VS2012 took out installer projects (instead telling you to just use InstallShield), SQLCLR projects, was incompatible with Oleg Sych's T4 Toolbox plug-in, and had a colour-scheme in the TFS source browser that made my eyes want to bleed.

Every other VS upgrade has been comparatively painless. I can't say I'm excited to try VS2013.

Re:Visual Studio 2013 released to web by duiker101 on Thursday October 17, 2013 @08:51AM (#6564991)
I think the problem here is that VS needs to satisfy the needs of many different types of developers and also try to appeal each ones personal preferences.

Personally I am enjoying VS2012 a lot and it is really sad that there are hardly other IDEs this good.

Re:Visual Studio 2013 released to web by at-fates-hands on Thursday October 17, 2013 @10:53AM (#6565721)
I completely agree. I've gone through plenty of good IDE's in the last year. From Dreamweaver, to Text Mate, to Komodo, to Aptana.

I started using VS when I landed in a .Net shop and it made sense to use it. Totally blown away by some of the cooler features you can't find on any other IDE. Even the free VS Express (which I now use at home) is so much better than other IDE's out there.

Re:Visual Studio 2013 released to web by eropple on Thursday October 17, 2013 @05:19PM (#6568194)
What features does VS2012 have for .NET (IDE features, not platform features) that don't have direct analogues in IDEA?

For C++, I find VS rather lacking compared to Xcode (though that's a combination of the compiler being dumb and IntelliSense being poor).

Re:Visual Studio 2013 released to web by _pmf_ on Thursday October 17, 2013 @09:22AM (#6565131)
> I think the problem here is that VS needs to satisfy the needs of many different types of developers

No, it does not need to. Someone decided that it needs to pander to web monkeys instead of empowering users that have used VS for 10+ years.

Re:Visual Studio 2013 released to web by untog on Thursday October 17, 2013 @11:46AM (#6566131)
Someone decided that it needs to pander to web monkeys instead of empowering users that have used VS for 10+ years.

Which it probably does, given the huge amount of development that is web-based these days. The market for Windows-based C# applications is shrinking by the day.

Re:Visual Studio 2013 released to web by archon on Thursday October 17, 2013 @09:37AM (#6565225)
> pander to web monkeys

Really? How exactly does VS2012 pander to "web monkeys" at the expense of others?

Re:Visual Studio 2013 released to web by anton_gogolev on Thursday October 17, 2013 @10:00AM (#6565353)
It's not necessarily "monkeys", but, disturbingly, Microsoft developer tools are becoming more and more oriented towards "wizard-and-designer-clickety-clickery" type development.

There are a few exceptions to this rule (think EF Code-First), but that's a drop in the ocean.

Re:Visual Studio 2013 released to web by lucisferre on Thursday October 17, 2013 @10:26AM (#6565536)
If anything MS tools have moved away from clickety-clickery. That was something they were pretty much famous for back in 2008. MVC and EF are just a couple examples of moving away from this patter. This is nothing but imaginative revisionism.

Don't get me wrong, this type of thing drove me from the MS ecosystem a while ago now but they do move largely in the right direction, just too slowly for my tastes.

Re:Visual Studio 2013 released to web by sk5t on Thursday October 17, 2013 @11:34AM (#6566035)
Agreed - EF code-first, Nuget, and ASP.NET MVC in general are excellent steps in the right direction away from excessively tool-oriented / ultra-bundled / abstracty type things. The very dark days were pure ASP.NET web forms with controls, DataSets, DataTables, ClientScriptBlocks, and the like.

A lot of things in VS are wrappers around very well-documented CLI tools, e.g., svcutil, and I don't begrudge these tools for doing a lot of heavy lifting.

Re:Visual Studio 2013 released to web by daigoba66 on Thursday October 17, 2013 @10:10AM (#6565424)
I kind of disagree with this sentiment. From my experience the tooling around editing source files (csharp, razor, javascript, css) has gotten a LOT of love in the past 2 years. You're probably correct in that more work has gone into web development use cases over traditional desktop software, but not much seems to have been added in terms of "visual" programming.
Re:Visual Studio 2013 released to web by anton_gogolev on Thursday October 17, 2013 @10:18AM (#6565481)
On the designer front I can think of Entity Framework designer and WWF designer, Build Template designer (or however this thing from TFS is called?) and possibly a couple more.

My biggest gripe are all kinds of wizards, most notably "New Project" ones. They do generate a lot of cruft I have to clean up later and pull way too many dependencies.

Re:Visual Studio 2013 released to web by matwood on Thursday October 17, 2013 @10:10AM (#6565420)
Microsoft developer tools are becoming more and more oriented towards "wizard-and-designer-clickety-clickery" type development.

Maybe you are just now noticing, but MS dev tools have always had wizard clicky things. For example, see the original Visual Basics from the 90s.

Re:Visual Studio 2013 released to web by anton_gogolev on Thursday October 17, 2013 @10:25AM (#6565534)
AFAIK, Visual Basic was targeted at non-professional/beginner programmers, so having wizards and designers is fine there.

My main gripe with abundance of today's "visual programming" is that we have memory-managed languages with immense expressive power and ability to write all kinds of DSLs, yet what Microsoft does is it provides crippled XML-backed designers along with half-baked frameworks and class libraries.

Re:Visual Studio 2013 released to web by Throwadev on Thursday October 17, 2013 @04:31PM (#6567932)
I've used VS for a few years, and have NEVER used any of the "visual programming" stuff.
Re:Visual Studio 2013 released to web by ConceptJunkie on Thursday October 17, 2013 @08:50PM (#6569146)
Microsoft has always had "half-baked frameworks and class libraries".

I actually like MFC, but it never really got past the "good for a first cut" phase, IMO. Fortunately, I've never had to deal with .NET, and besides a little MFC, most of my work is on Linux these days.

Re:Visual Studio 2013 released to web by chris_mahan on Thursday October 17, 2013 @02:39PM (#6567305)
All microsoft products are targeted at purchasing decision-makers.
Re:Visual Studio 2013 released to web by rschmitty on Thursday October 17, 2013 @10:29AM (#6565551)
Ya, I can't begin to tell you the number of times I have been made fun of by ___ text editor fanatics for using an IDE that has wizard clicky things/drag drop components etc

http://www.youtube.com/watch?v=hkDD03yeLnU things like this never help

Re:Visual Studio 2013 released to web by jbigelow76 on Thursday October 17, 2013 @11:00AM (#6565767)

    >Microsoft developer tools are becoming more and more oriented towards "wizard-and-designer-clickety-clickery" type development.
Weird, I have the exact opposite impression. It seems like forever ago that VS was touting things like drag and drop design or wizardy stuff.
Re:Visual Studio 2013 released to web by taspeotis on Friday October 18, 2013 @12:14AM (#6569738)
Yeah, I'm so spoilt with all those wizards VS gives me for editing MSBuild targets...
Re:Visual Studio 2013 released to web by jameshart on Thursday October 17, 2013 @11:13AM (#6565865)
The powershell prompt to manage your nuget package dependencies on a project is pretty much the opposite of 'clickety' development. The F# interactive prompt, likewise.

MS have always done a good job of catering to a wide range of developer personas.

Re:Visual Studio 2013 released to web by plaguuuuuu on Thursday October 17, 2013 @10:44PM (#6569490)
Enterprise developer here. That wizard bullshit is 100% enterprise. It's horrible to use and only exists because most enterprisey programmers are too terrible to grasp more productive coding methods.

Still 100x better than digging through 100 pages of abstruse Java docs about AbstractProxyBeanDAOFactoryProxy.GenerateAbstractProxyBeanDAOFactoryAccessor though.

Re:Visual Studio 2013 released to web by ern on Friday October 18, 2013 @05:01AM (#6570419)
It's weird, because my experience of .NET enterprise development recently has been of people with Java-envy needlessly using Unity, and every other enterprisey framework they can get their hands on, for even small projects.

Closer to this: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... than drag and drop, clickety-click.

Re:Visual Studio 2013 released to web by zwieback on Thursday October 17, 2013 @11:47AM (#6566141)
I felt that way when I switched from m.exe + cl.exe to Visual C++ but I eventually got over it. There's actually some pretty cool stuff happening at the lower levels, check out the "Going Native" stuff on Channel 9.
Re:Visual Studio 2013 released to web by bitwize on Thursday October 17, 2013 @03:09PM (#6567492)
It's not necessarily "monkeys", but, disturbingly, Microsoft developer tools are becoming more and more oriented towards "wizard-and-designer-clickety-clickery" type development.

The term "wizard" came about because of the AppWizard and ClassWizard features in Visual C++.

Clickety-clickety has been a goal of Visual Studio since before it was Visual Studio.

Re:Visual Studio 2013 released to web by gcb1 on Thursday October 17, 2013 @12:53PM (#6566566)
you are right. vs wizards were mostly limited to visual basic. now vs is vb.
Re:Visual Studio 2013 released to web by mkohlmyr on Thursday October 17, 2013 @10:03AM (#6565366)
"web monkeys" Cute. Meanwhile you're the one developing in VS on Windows.
Re:Visual Studio 2013 released to web by overgryphon on Thursday October 17, 2013 @02:21PM (#6567184)
I don't think the comment was intended to be derogatory towards web programmers, so much as annoyed at the "you can create a website in an hour without writing a line of code" oriented features. Some of the web-oriented stuff in VS over the last several years seemed to be targeted towards mouse-oriented design of small web apps rather than more serious web programming. I do not think that is still the case, though I haven't really been paying attention.
Re:Visual Studio 2013 released to web by Finster on Thursday October 17, 2013 @05:02PM (#6568101)
FWIW, I can build an app in html5/javascript for every major desktop and mobile platform that runs "natively" on the host OS.
Re:Visual Studio 2013 released to web by daigoba66 on Thursday October 17, 2013 @08:25AM (#6564877)
For installers, use http://wixtoolset.org/.
Re:Visual Studio 2013 released to web by anton_gogolev on Thursday October 17, 2013 @09:00AM (#6565025)
Yeah, because I really want to spend hours upon hours studying obscure incantations that someone decided to be making sense.

WiX (and MSI, for that matter) is a disaster.

Re:Visual Studio 2013 released to web by DrJokepu on Thursday October 17, 2013 @09:12AM (#6565085)
It’s really not that bad. WiX is actually pretty decent, definitely not a “disaster”. It might look more frightening than InstallShield because you don’t get a nice UI that allows you to set up an installer with a few clicks, but I mean, we’re programmers here, surely editing textual configuration files is not an issue? It took me somethong like 30 minutes to replace our old InstallShield installer with WiX.
Re:Visual Studio 2013 released to web by coffeeaddicted on Thursday October 17, 2013 @09:35AM (#6565218)
I gave it a shot for a day recently but found it way harder to use than InstallShield or NSIS. Part of it was probably the broken documentation where half the links just ended in nirvana. But I gave up when I learned you really have to add each single file one-by-one and the documentation even defended this as a feature.
Re:Visual Studio 2013 released to web by euroclydon on Thursday October 17, 2013 @09:50AM (#6565297)
You can use this Wix tool or command called Heat, which will automate the adding (and creating GUIDs) for a bunch of files. Really it's the underlying MSI target that's so painful, especially when you get into versioning. The OS wants to have detailed information on every file that is part of your installation. I think this is primarily for uninstallation purposes, but also for upgrades and who know what else. If I could get away with it, I'd just use NullSoft. It's like writing assembly, but it's so much simpler.

With Wix/MSI, there were certain executables that I could never get it to run as part of the install process. The XML would look the same as other execute commands that worked, but I could never figure out why they didn't run.

Re:Visual Studio 2013 released to web by anton_gogolev on Thursday October 17, 2013 @09:54AM (#6565317)
Amen.

This can "kinda" be worked around with "heat.exe" (don't get me started on naming of tools in the toolchain), but even then you'll need to explicitly specify half a dozen command-line arguments (-ag -dr -cg -srd -scom -sreg -svb6 -sfrag) to make the thing work.

Re:Visual Studio 2013 released to web by powertower on Thursday October 17, 2013 @10:01AM (#6565356)
So how would one deal with projects that contain 1000s of files?

Run a script to enumerate the files and populate a wix file? Zip up the different parts and have the installation process unzip them?

Re:Visual Studio 2013 released to web by anton_gogolev on Thursday October 17, 2013 @09:35AM (#6565219)
Don't mean to sound like an ass, but oh really?

WiX is a thin wrapper around MSI (which sucks beyond belief) and as such it suffers full blast from all the "design" decisions of the latter, not even trying to remedy the situation.

I really could pour out a full-blown rant on MSI in general and WiX in particular, but that would be wildly offtopic and of no interest to fellow HNers.

Re:Visual Studio 2013 released to web by ConceptJunkie on Thursday October 17, 2013 @08:52PM (#6569158)
If you think MSI is bad, and I'll have to take your word for it, what MS had prior to it was probably worse. Writing installers for Windows using MS tools has always been a nightmare.
Re:Visual Studio 2013 released to web by eropple on Thursday October 17, 2013 @05:23PM (#6568221)
He's not wrong: WiX is a horrorshow. It's unintuitive, difficult to read and parse, and is saddled with much of the cruft of years of Windows; when you compare it (or NSIS, or InstallShield) to building an .app (or even a .pkg) under OS X, it fares very poorly.
Re:Visual Studio 2013 released to web by breischl on Thursday October 17, 2013 @10:42AM (#6565654)
Wait, weren't you complaining about all the "wizard clickety clicky" things in another thread?

If you hate wizards, and you hate "obscure incantations", which I'm assuming means code, then what do you like? Do you program in natural language with voice recognition?

Re:Visual Studio 2013 released to web by anton_gogolev on Thursday October 17, 2013 @11:01AM (#6565774)
Where's the conflict?

By "obscure incantations" I mean having _three_ different syntaxes for string interpolation/variable substitution, providing _six_ command line arguments for the tool so that it does the one reasonable thing, having illogical rules in comparison operators, having to use a frickin' _bootstrapper_ to install prerequisites and not being able to chain MSIs, not being able to have a single installer for x86 and x64, not having a _simple_ way to define logic for "Back" button, yet having to write heavily nested XML to do simplest thing.

Re:Visual Studio 2013 released to web by roel_v on Thursday October 17, 2013 @09:19AM (#6565115)
The same can be said of programming in general.

It's true that msi is different from other installer builders, but it's for a reason. And if you have a concrete project you can build while following along with the wix tutorials and book, it's not difficult, it just takes some time.

Re:Visual Studio 2013 released to web by anton_gogolev on Thursday October 17, 2013 @09:39AM (#6565237)
Yeah, the "reason" being that Windows Installer was designed to support corporate deployment of applications to shared machines with install-on-demand and roaming profiles, and to support Windows 95 and up. This, and Microsoft's manic affection to backwards compatibility plus "architecture astronautery" (on-demand installs of COM objects, anyone) makes MSI a disaster.

The fault of WiX is that it's too thin of a wrapper.

Re:Visual Studio 2013 released to web by jaredsohn on Thursday October 17, 2013 @01:28PM (#6566786)
I've always liked InnoSetup (http://www.jrsoftware.org/isinfo.php). You describe your installation in a short file created via its syntax-highlighting IDE. A big con is that its scripting is done in Pascal, but you can likely find existing scripts to do many common operations.
Re:Visual Studio 2013 released to web by Pxtl on Thursday October 17, 2013 @09:39AM (#6565236)
While that's obviously a solution, it's not quite the same y'know? There's a lot more skill overhead in learning that tool vs the comparative ease of the installer project.

Considering how thoroughly MS screwed the pooch on ClickOnce, I was genuinely surprised when they completely abandoned their working installer system.

Re:Visual Studio 2013 released to web by gecko on Thursday October 17, 2013 @09:45AM (#6565265)
What's wrong with ClickOnce? I've not used it from a developer's perspective, but Chrome's installation (which uses it) always seems smooth as butter.
Re:Visual Studio 2013 released to web by whazzmaster on Thursday October 17, 2013 @11:46AM (#6566127)
For small things ClickOnce is fine, but it's a pain in the ass to automate. For example, there's no way to synchronize the 'version' of the installer with the version of the EXE it's installing. I had to hack[1] it so I could pull the version metadata off the EXE assembly and then force it into the XML of the project file where the ClickOnce settings are stored.

There's also no ability to publish the built installer outside of the UI- my build scripts had to build the /app.publish directory and then just copy the whole shebang to a network location for deployment. I'm not as upset about this being a separate step, but if they indeed allow you to configure and deploy the installer from within the UI why not expose an API to do it as well?

Overall I think ClickOnce is fine for internal, self-updating tools. It's worth noting, however, that I was inspired to create my workflow based on looking at what Github was doing with their windows client.

[1]: http://whazzing.com/blog/2013/04/11/automated-clickonce-buil...

Re:Visual Studio 2013 released to web by jonnii on Thursday October 17, 2013 @09:52AM (#6565309)
There's a lot of things wrong with ClickOnce. IIRC chrome's installer only uses clickonce as a bootstrapping mechanism for the _actual_ installer.

Problems:

* Can't choose installation path * No offline installation * Hard (impossible?) to use with a CDN.

Here's an example of how to turn a directory of precompiled binaries into a click once package using powershell:

https://gist.github.com/jonnii/2628150

My powershell isn't _great_, so forgive any powershell oddities, but notice how much you have to massage the output of the mage tools to actually get it to do what you want.

Re:Visual Studio 2013 released to web by nickpp on Thursday October 17, 2013 @09:33AM (#6565200)
Or Advanced Installer's free edition if you're xml-challenged.
Re:Visual Studio 2013 released to web by jonnii on Thursday October 17, 2013 @09:48AM (#6565289)