Visual Studio for Mac
msdn.microsoft.com
msdn.microsoft.com
[1]: http://useyourloaf.com/blog/xcode-visual-memory-debugger/
- Don't throw all your screens into one file, you can even use one screen per file just like xibs
- Use code to style items and create controls you use more than once
- Render all the controls in code dynamically in interface builder so you won't end up with "ghost town" storyboards but everything is visible at a glance
Unless you're working at "Facebook scale" Interface Builder in the hands of an expert will get you very far.
Would you throw all your code in one big 8kloc controller? Of course not, but somehow people manage to cram every screen into the same .storyboard file, just because you can do it. Then they'll complain about merge conflicts, which isn't really a surprise given the fact that you're managing an 8kloc file.
Would you set the background, border, font and color of every button every time you use it in code? Of course not. You specialise a button class. But somehow people are selecting every button manually and setting those properties time and time again once they start using Storyboards while you can use a specialized class that will render in Interface Builder exactly like it will look in the app.
How do you fix these issues?
- Fixing misplaced views when transitioning from retina / non-retina screens or even different retina screen resolutions.
Reasoning: When I worked at Amazon this was extremely annoying - You didn't even have to touch the storyboard, you only had to open it and tons of misplaced views showed up. This causes a problem when working with any version control system because the XML changes are reflected in git even though nothing actually changed.
- Rendering Snapshots
Reasoning: I use snapshot tests to verify all views via unit tests. You can use IB to capture the view and load it programmatically, but you end up having to load the whole storyboard just to render one view controller.
- Setting all properties via IB
Reasoning: When I setup a button or a view, if half of my properties are in IB and half of my properties are in code, how do you determine what goes where. Apple did add IBDesignable, but wiring that up is so that you can click a drop down is more complicated than just setting the property on the object (and it renders in snapshots correctly and it never suffers from misplaced view and property configurations are in one place).
The teams that I've worked on aren't that big, but I can say that teams I've been a part of that don't use IB have worked a lot faster than IB teams. You may be a lot better at IB than I am, I only stopped using it 1 year ago for my projects after about 4 years of using it.
I've had several people at Apple tell me they generally don't use interface builder internally.
I recommend this video to see some good example about reverse debugging with gdb. https://www.youtube.com/watch?v=713ay4bZUrw
This is extremely dishonest assessment that only 'Developers' do professional work. Mac is used by Engineers, CAD/CAM, designers, illustrators, artists, musicians, etc and to reduce it only to developers is disingenuous.
I for one is happy with the new Mac and there are several people who've found it great for 'pro' use.
Engineers, CAD, musicians, 3D artists all need more power than it provides and increasingly need CUDA cores.
I'm running a Logic set up on my 2012 MBP, and I've never felt limited by its capabilities. I've been running Macs for music production for almost 20 years, and in my experience they have all at some point not had quite enough in the bag to let me do what I wanted of them. This is the first one (now fours years old) that has stayed ahead of my needs. I can run multiple copies of Massive, and rows of Waves plugins no problem.
I have hit limits with real-time 3D stuff, like gaming and Houdini, but music production is still well within its capabilities for me.
The main gripe musicians have with apple is the new OSX breaking their setup every year. The sandboxing in el capitan was particularly disastrous.
This is beyond hyperbole.
I used Windows when I was young, then switched to Linux for 10 years professionally, and finally I switched to the Mac about 5 years ago. I find it much easier to use day-to-day than Linux. Especially using multiple displays in different offices.
http://www.huffingtonpost.co.uk/thomas-grove-carter/one-prof...
Spoiler alert: he doesn't agree with the assessment of HN users who haven't actually used it.
All I really know about this is how I feel about it and I must admit that I am going to go back to the PC world when the time comes to replace my current MBP. The offerings in the PC world are not perfect for me but they suit me better. I bought my MBP because at the time it was actually the cheapest machine offering all those features at a high build quality. I didn't get into a dependency on OSX and am pretty confident that I can just migrate fully to Linux. So I guess I'm not _really_ a professional Mac user.
99.9%+ of criticism of the new MBP has been of the form "Without ever interacting with one, I can tell it is unsuitable for me and therefore is unsuitable for anyone, anywhere, in any professional purpose, ever".
no-true-Scotsman-fallacy of "Noone who _really_ used it dislikes it."
More like "people are pre-emptively concluding, without ever having so much as been in the same room as a new MBP, that it is the antithesis of everything they need from a computer".
Which is, to put it bluntly, idiotic. I've suggested in the past that this feels less like "I have legitimate criticism of this product" and more like "I hate the manufacturer, always have hated and always will hate the manufacturer, and see this as a convenient cover for venting my hatred of the manufacturer". Notice how much of the criticism veers quickly away from specific aspects of the product and into "this is classic Apple", "this is how Apple treats users", "this is what's wrong with Apple", "Apple abandoning a key segment again", etc.
While this some truth in it, it is not what I took away from the discussion. Most people complain about the following:
* "I expected more."
* "I expected the price for the same specs to drop or at least stay constant but not to rise."
* "I cannot use this machine to do the work in the way I do it currently. This and that port is missing."
While there is a great deal of hate towards Apple, the comments I've read here are not driven by hate but by disappointment. The old MBP lineup was very good for these people. They like them very much. Some love Apple, some don't care but they all agree that the old hardware is very solid for a reasonable price.
I really do think that the new MBPs are good machines for >90% of the current MBP users. A bit more expensive but not too unreasonable given that most are locked into the Apple ecosystem. Some may need some adapters for things like digital cameras, projectors, monitors, USB sticks, keyboards etc. but that doesn't really matter to a true Apple customer. Most of the time the machine is used without those devices.
What Apple should worry a bit about, though, is, that the top 1-3% users are now looking for other hardware. But who am I to worry about Apples strategy. Probably they don't need those few powerusers anyways in their future business model. I don't even hold Apple stock currently. My old MBP runs fine still and I'm not locked into their ecosystem. I can move onto the greener lawn at any time.
The mac I'm currently using was purchased 3 years with 16GB of RAM and if I replace it I will be stuck with the same capacity. I imagine there are a lot of "Pro" market segments that are well served by 16GB or less though. I'm hoping the next revision gets a >16GB capacity and it's released before I need to replace this one.
I've been around the consumer tech industry a long time. I've shipped a considerable amount of consumer computing gear and am very familiar with the design process and the many tradeoffs that happen when you take something from a cool idea to heavy in someone's hands. One of the places I did this was Apple, in fact.
Apple seems to have decided to shift the market for the MBP by making tradeoffs that don't target any of the professionals I know.
I also know that (a) my predictions about the hardware were correct, and (b) none of the professionals I know plan to buy one, beyond the one or two samples we're getting into our group just to make sure we're making the right decision.
And now we're looking at Linux laptops in a serious way.
Professionals, yup.
Many of the complaints are about plain old hardware specs, especially RAM and the USB-C connectors. You don't need to hold a MacBook in your hands to understand how much RAM it has and how many dongles you'll need to buy. Same for complaints about the price.
I use Mac, windows and Linux daily... And honestly the Mac is the most odd ui of the three for me. Having bash is pretty nice as is homebrew...
I'm really hoping MS puts similar effort into a Linux version, since I know I'm not the only one going that direction... Been considering it on my mbp...
The only thing it doesn't have is the battery life of the MBP, but if you want raw power, you may be plugged in most of the time anyway.
No matter what you think the specs say, the fact is the software and hardware are so well integrated
it tears strips off "superior spec'd" Windows counterparts in the real world.
This has always been true of Macs.
In "professional" situations this is not, as I understand it, particularly unusual. And yet the unsuitability of the new MBP for "professional" use cases has been widely assumed on HN. It's interesting to see someone who actually has one of those use cases and has actually used the new MBP, weighing in to say "it works, and here's why". Not least because the level of hardware/software cooperation Apple can muster is a selling point for him, but has been ignored by all the "I'm a touch typist whose workflow consists exclusively of function keys, the touch bar makes this a worthless toy to me" noise coming from HN.
So not a programmer, and not someone who was using the function keys in the first place based on that article. Furthermore he claims it's "faster than editing on any windows system" because Final Cut Pro X is integrated so well with the hardware he doesn't need more memory or CPU. Sorry, of all the applications he could've chosen, claiming that a Windows box with more memory and a better CPU would be slower is... asinine. Fanboy alert.
This is absolutely silly. A professional blacksmith can't work without a proper anvil. There really is something to be said about having proper tools for the job. You can't drive in a nail with a shoe, you'll need a legit hammer.
No matter what you think the specs say, the fact is the software and hardware are so well integrated it tears strips off “superior spec’d” Windows counterparts in the real world.
could the statement be any broader? what are the "superior spec'd windows counterparts in real world" he's compared it to? Also he's using Final Cut Pro which happens to be an Apple product so if that's faster due to integration how does that help anyone using non apple development software which I presume is majority of macbook pro users. I edit a lot of photos and I don't use any Apple software for it
On one hand microsoft stepped up their attention to individual professionals (e.g. designers, developers, etc., more or less like Apple 15-20 years ago) and apple seems to forget them.
On the other hand, microsoft is infamous for privacy, for their forced upgrades, their updates, whereas apple emphasizes privacy.
I like macbooks as laptops, but on software front apple seems to rest on their laurels and developers seem to use macbooks, either because unix or there's more money in App store than elsewhere.
"Why would you buy a PC anymore?" - Tim Cook on the iPad Pro launch.
Don't be surprised if XCode for iPad Pro is a thing soon. It's becoming clear he sees iPads as the future of computing, it's all he uses personally and developing it's own apps is one of the last things it actually can't do.
Also developers like to you use their own tools. That doesn't fit well with the "you will do as you are told" approach of Apple.
I don't use it 100% of the time (I also have a desktop machine) but it works extremely well and offers me things that a laptop cannot.
EDIT: It also doesn't have an Escape key - but I use Ctrl-C in VIM as I don't have to move from the home position then
My set up proves you wrong: Nexus 7, bluetooth keyboard, a Debian chroot with git, vim, python and apt. I take that with me to sketchy places instead of my laptop. I think a 10-inch tablet could be more comfortable to read, but I love the Full-HD screen and pocketability of the 2nd-gen N7. I find it amazing that 3 years later and no other Android tablet has a screen resolution that's comparable.
That said, I'm happy to see this and do hope to see a similar effort for Linux as many Mac users are starting to move on. This may well be an indication that the next VS on Windows may well be based on the MD base... Should they want to unify that.
I've been very happy with VS Code for my needs all the same. Can't recommend it enough for js/Node.
I have no idea what these self-appointed "pros" actually do. Their work seems to involve a awful lot of swapping hardware components, attaching peripherals in a jurisdiction that frowns upon adapters, and pressing ESC.
Mobile CPUs are approach mobile core 2 duo performance.
The second either is added to the project, you will need a much more powerful computer.
it's not needed if you're building a JavaScript app with Sublime text.
But compiled environments such as .Net take a lot of cpu and memory. It's not uncommon to have 2-4 visual studios open which can take up 10 gigs of ram. Couple that up with continuous build/unit test frameworks and 5-10 VS add-ons and you need a powerful machine to make it responsive
These days a typical developer laptop is 5x more powerful than the system the code will be used on (mobile device, virtual server, etc.)
I am a developer and I could not care less about function keys.
Why the duck would developers need function keys? Even for Vim, the age-old advice is to remap Esc so that you keep your hands on the home row.
A flexible multi-touch strip of context-aware keys can do much more things -- e.g. map debugger step moves when I'm running an IDE, or trigger builds, show the SCM status of the current opened file, etc.
What should I do instead? Serious question.
If you're using Windows, the F keys appear on the Touch Bar. /story
Use the strip bar in debugger keys mode, or function keys mode for non-updated apps?
Or use printf statements (seriously -- I never advocated for much debugger use, unless it concerns very focused stepping. A lot of people step all around and examine everything and anything for ages with no clear idea of what the bug might be).
I remember the time when everybody was getting one of these: https://elitekeyboards.com/products.php?sub=pfu_keyboards,hh...
Apple tinkering with the function keys has allowed the development community to recongratulate themselves with IDE it seems.
Seems also that people confidently touch type debugger instruction, despite the key that you want being literally squeezed between 2 keys that will ruin you debugging session and make you lose the next 10 minutes.
I think the developer community at large is more prone to overreaction.
Note that I think people are going to be impacted. I think the touchbar is a downgrade for people that needs to use Windows either in the VM or Bootcamp. Some IDE are especially F-keys happy like Eclipse will be slightly worst of.
I still type on an old MBP with physical F-keys and they are actually awful for touch typing. They are smaller, evenly spaced (no grouped) and not aligned with the lower key rows. If you are serious about touch typing potentially workflow ruining key combination like debugger ones, you must use an external keyboard already.
And used the 2nd function (volume brightness etc) as the default for touch bar.
That way the touch bar is useful and functionality of function keys is kept. I would have bought the new mbp if that's what they did.
Now I'm going to get a dell :/
Give it a year or two, and most PC laptops will come with a touch bar.
From the exterior (I'm too young and the only Mac I've ever used was the Macintosh Plus -bragging, with 4Mo of RAM- while I was a child), it really seems like Apple has dropped the ball for professionals, both developers and graphics people.
There are now equally well designed PCs (laptops and desktops) from other manufacturers, Windows has a lot of support, if you want to use Linux, the kernel now supports a wide range of hardware.
In the meantime, Apple doesn't have a good desktop offering, and their laptops seem gimmicky to me while not offering a performance edge over their competitors.
A few months ago I thought about buying a (my first) Macbook and waited for their announcement, now I'm looking the other way.
And around me, I'm the guy people go to ask when they have a computer related purchase to make.
That bit is debatable.
I see machines like the HP Spectre and feel they are still somewhat overdesigned.
Mac have never been "for Pro" if you go that way. So I guess it confirm that it's not the company that shifted it's focus, but maybe there is more potentials customers expectation of Apple going more "pro".
Yes, Apple has never targeted businesses, but they did target individuals professionnals at some point. Video and sound editors used to work on Macs, and now move to windows. It's a classic, but is it wrong?
https://webcache.googleusercontent.com/search?q=cache:Vk2On-...
Maybe a Feature Request for HN, would be for a 'alt' link (that mods update) as part of the clickables under the post title?
This would save people manually posting these all the time and would, in many cases prevent the case where it becomes impossible to retrieve a cache, because nobody thought to access one before the slashdot effect occurs. Or, as in this case it seems, the article is pulled.
It would also be nice if, 24-48 hours after submission, the only cache link remaining is archive.org (if they have the page), so the content is retained permanently as-submitted. It's rare, but sometimes a page will be updated so the comments no longer make sense.
It would also be nice to include a link history in the same area (have requested this before), in case the original submission is changed by the mod. Usually when this happens the notice is the top comment, but sometimes it isn't and the discussion can be quite confusing as a result.
Here's an internet archive link that works for me: https://web.archive.org/web/20161114070745/https://msdn.micr...
Edit: Thanks for the tip BTW. I had linked to this from a blog post, but have now removed the dead link (https://unop.uk/cross-platform-native-mobile-app-development...).
I actually prefer Xamarin Studio over Visual Studio (on Windows) in some respects. For example, the Xamarin.Forms XAML previewer is much better. Looking forward to a full designer.
P.S. I've got a four part blog post series this week on Xamarin.Forms. Starting with this today: https://unop.uk/cross-platform-native-mobile-app-development...
MS is going all Oracle-y on us, withdrawing from the consumer market as fast as they can, and heading for the green pastures of the corporate market, where fat happy companies are there to be milked. They are sick and tired of fighting for consumer money one penny at a time.
(XBox is probably not long for this world either.)
But most people writing the apps which then run on Linux, develop them on Macs (and the point of WSL is to give them a reason to consider Windows for this).
It still has a few bugs and hangs up on me once or twice a day. I think they should have those ironed out soon though.
By the way, since it's based off MonoDevelop, you can just use it con Linux.
Why is this a bad thing? Microsoft is a company, they exist to make money. A huge new market for them is 'Cloud' and they're doing everything they can to make that as appealing as possible.
Back when they made money from selling operating systems, they were definitely doing some tree chopping with some of their practices.
Back when .Net was Windows only, they gave it away because the goal was the developers would pay a lot of money for MSDN, GUI apps on Windows, SQL Server, Office, and Sharepoint integration, etc. But .Net core is mostly server side, so I'm having trouble figuring why they'd bother giving away VS to Mac users without being forced to run on Azure in production.
It's the trickle up theory of modern development. Get folks using your languages and tools, and if you make it easy to integrate with your cloud services in those tools, that's where the revenue comes in.
It's probably an interesting number how much revenue is generated by various cloud providers for folks who just forgot to shut down their VM
"""For the functional programmers among you, it includes excellent F# support, powered by the same F# compiler used in Visual Studio."""
I've heard that F# is great from multiple people I trust a lot (and a quick cross check showed it does indeed look very cool) so I might give it a try once this is released.
I do some C# development (Unity Engine stuff) on my Powerbook so this is also good news (MonoDevelop is fine but I'll obviously test VS for Mac)
1) Visual Studio for Windows (C++, I assume?)
2) Visual Studio Code (Javascript, Atom)
3) Visual Studio for Mac (C#)
it actually says it supports c++,c#... I still dont get what the difference is..
Having only ever developed on linux I am actually slightly excited to use an IDE like visual studio after seeing some people at work use it..
Visual Studio Code is a text editor built in TypeScript and based on Electron. It supports a broad range of languages, but it's an advanced text editor, not a full fledged IDE
-VS Code doesn't support solution-wide refactoring like renaming classes or moving a method from one class to another
-VS Code doesn't support runtime debugging (breakpoints)
-VS Code doesn't have a visual editor
-VS Code doesn't have memory or performance profiling tools
-VS Code doesn't have source control integration
-VS Code doesn't have an integrated build tool (MSBuild)
-VS Code doesn't have NPM or Nuget integration
> VS Code doesn't support solution-wide refactoring like renaming classes or moving a method from one class to another
F2 "Rename Symbol" (works on Go with gorename). Can't imagine using Roslyn doesn't (or won't soon enough) allow the same. From the readme:
Great C# editing support, including Syntax Highlighting, IntelliSense, Go to Definition, Find All References, etc.
> VS Code doesn't support runtime debugging (breakpoints)
It does. CMD+Shift+D goes to the Debug sidebar. CMD+Shift+P Debug shows a bunch of commands. From the readme:
Debugging support for .NET Core (CoreCLR). NOTE: Mono and Desktop CLR debugging is not supported.
> VS Code doesn't have source control integration
CMD+Shift+P git whatevs is used daily here as well as Ctrl+Shift+G for the git sidebar that can show (editable) diffs. Both the gutter and scroll bar are annotated with git info.
> VS Code doesn't have an integrated build tool (MSBuild)
MSBuild comes with .Net Core and is (probably) invoked with the language-agnostic CMD+Shift+B (run build task). C# ext may have more.
> VS Code doesn't have NPM or Nuget integration
There are both NPM and NuGet extensions available.
Now of course if what you want is all of this nicely packaged and wrapped in a GUI, well, obviously VS Code is not an IDE (as VS is) but that's precisely its value proposition.
The GP was looking at the languages the tools were written in, not the languages they support.
For what it's worth, I believe 'TypeScript + Electron' would be a closer description of what VSC was based on.
It's not that it doesn't do the job, it's just a different workflow.
As it stands, VS Code is probably the best tool for JS/Node projects or today imho. And from what I've seen, one of the better options with plugins for go and rust.
It's also available for Windows, Mac and Linux... Much faster/lighter than others, including Atim.
I'm a fan of code, but no ties to ms...
Most of the UI was rewritten for VS2010 with WPF (XAML, DirectX acceleration), but lower/deeper parts are written in c++ and this makes porting "probelmatic" (MFC, win32.dll, kernel.dll to posix stuff).
MonoDevelop ~ Xamarin.Studio is written in C# (some plugins in F#) and this makes porting easier. That is the reason there was MonoDevelop version on Windows.
They ran into a dead end and changed the strategy. They can change it again. Utimately, money decides.
I don't want to learn C# to write iOS apps. I might learn it just for fun, but I will continue writing the iOS apps with Swift/Objective-C and C++.
C++ support is the weak spot of Xcode and so far I haven't found a suitable IDE for C++, except maybe Qt Creator and several IntelliJ-based IDEs, which are ok but not on par with Visual Studio on Windows.
I keep a windows machine around mainly for writing C++ code (and games!).
I also like Swift a lot. It's a modern language with lots of powerful features and also very practical.
My current project involves a lot of context switching between Swift, C++ and Objective-C++ and I miss a lot of Swift's features in C++.. For some obscure reason I also enjoy Objective-C++ quite a bit, it's a weird mixture of insanity but it feels good ;).
I don't know a lot about C#, I think it must be a good language, albeit older with more historical baggage, but even so I wouldn't use it instead of Swift for iOS development.
I mean, why ?
For Android development - maybe - I'm not too fond of Java, but on iOS/Mac - I will stick with Swift thank you.
I like to use Eclipse CDT or Netbeans when I am on UNIX.
But in the past one year, Microsoft has got me in again: a. Moved to TypeScript from JavaScript (including my hobby projects) b. Moved to VSCode from Sublime c. C# is a great language and I just hate Java. Hope this and more steps make it easy to use C# and deploy in non-MS environments.
> At Connect(); in November, Microsoft is launching a preview of Visual Studio for Mac.
Does it have a monolithic install and update process that's essentially a slow, bloated black box? That's my main turn-off with Visual Studio on Windows, and even more so with Windows itself.
As soon as Microsoft figures out efficient installation and updates via CLI without the need to reboot, they'll dominate the developer space (and perhaps server market, where reboots are even more problematic).
Smallest install is 500MB
.NET/C# install is ~3GB
I also believe you won't have to reboot with most installs.
Visual Studio for windows has two different "cores": the massive old C++/COM-based application used since forever, and the newer subsystems Such as The language subsystem (For C# and VB) Roslyn, which is .NET based.
Xamarin Studio could be using Roslyn, but the app isn't based on the same platform as VS itself is. Since it is at it's core a newer and much smaller application, it shouldn't have to have any of the setup issues that VS has (just like VS code doesn't).
I think it will be better to wait for release of Project Rider. At least EAP is already available
Other project types were added recently and I haven't tried them yet, so I would not like to speculate.
Though there are projects that might indicate something (SkiaSharp and VulcanSharp) on mono project github organisation.
The developers that have still not abandoned WinForms will not jump shit when the next thing hits either. To keep the huge group of WinForms developers happy, Microsoft will continue to support and develop Winforms. For many, WinForms are still the fasted way to develop simple applications.
So if you want develop for the Windows (desktop) platform, WinForms will be a clear winner for many many years into the future.
WPF is based on XAML and XAML is the future of UWP.
Just because the API is a little different it doesn't make it in life support, also there were updates on .NET 4.6.
As for Windows Forms, it is officially on life support as communicated at BUILD 2014.
PS. According to me it was difficult to port the Graphic part of WPF to Linux/Mac.
I wonder if it will continue to support Android, or if there will be a Linux release.
I've heard good things about it, and just this past weekend tried it out, but couldn't even get a simple Hello World working on it for Python.
I installed the common Python extension for it (Don Jayamanne's), but seems like it couldn't Link with the Python toolset. Ie, I could edit scripts with Python highlighting and autocomplete, but couldn't get them to execute. I gave up after an hour of trying and went back to pycharm.
I'd be interested in giving it another go, but worried if I'm needing to bang my head just for a Hello World, how bad it might get later on.
Have you set the configuration setting for the python executable?
"python.pythonPath": "/usr/bin/python",
.NET open source and officialy supported on *nix, some version of SQL Server on Linux, cross platform Visual Studio Code editor, now Visual Studio for macOS...
Unbelievable.
Next up, when is VS for Linux?
There doesn't appear to much demand for our product on Linux - it's targeted towards quite a conservative and on-tech market - but Linux support would also be very welcome.
https://blogs.msdn.microsoft.com/vcblog/2016/06/07/visual-c-...
Till date I cannot find anything Android related in MonoDevelop (or its available Add-ins).
What's Microsoft's game plan with this? Are they trying to drive more people towards Azure?
I wonder how this will affect Rider (the new jetbrains C# IDE based on intellij, currently in EAP) and if they will continue to invest in Resharper for multiple platforms, or focus effort on bringing the resharper functionality into Rider.
...I also can't help but think this sort of indicates that the C# tooling in visual studio code is being reconsidered; which seems reasonable, I was always disappointed by it.
It is a lot easier than Visual Studio Extensibility system.
I had a four part blog post series on Xamarin.Forms and .NET on a Mac planned for this week. Starting with this introductory post today: https://unop.uk/cross-platform-native-mobile-app-development...
But if the past holds any indication for the future, then I'm not holding my breath for it. They'll probably just use the Mac version to introduce slight incompatibilities or make the Mac versions of existing products kind of slower and buggier than the Windows versions. :(
Everything made by Xamarin was opensourced in 2016-04/2016-05 under MIT license, so it cannot be vendor locked anymore.
Presumably, C#, Android, and iOS are their top priorities to support, things like VB are less so, but could be added later.
I wonder if this means SQL Server Express is coming as well, but that doesn't matter as much to me since I think Entity Framework takes care of working with a different database engine
I'd be more inclined to use react and Redux with electron. With Cordova to bridge to mobile.
Really do like VS Code.
Just my two cents.
Of course, you'd still need the assemblies - they could be extracted from .NET redist, but it's not easy.
I might have still some magazine lost somewhere about Visual Studion and MFC for Mac OS.
Can Mac users download this or not?
> We're sorry, the page you requested cannot be found.
"We're sorry, the page you requested cannot be found."
Google cached version: https://webcache.googleusercontent.com/search?q=cache:Vk2On-...