http://blogs.technet.com/b/keithmayer/archive/2013/03/20/managing-free-hyper-v-server-2012-with-a-local-gui-console-tool.aspx

I thought that I’d give Hyper-V core (free) a good go today for a couple of SME reasons.

Smaller organisations are often based in suburban areas & suffer power issues beyond their UPS capacity. Windows recovers better from sudden outages than linux based systems. (I believe that’s a benefit of Command versus Script based). Secondly, I was hoping to use it for 2 processor servers that are beyond the free version of V-Sphere. (Still not sure if that’s supported on Hyper-V free).

The end result is that I’ll just tell my clients to buy the essentials version from VMWare.

Even though I have downloaded a copy of Server2012 standard, I insisted on trying to set up the free core today. There is a lot of misinformation out there & I might just have read most of it . I should be setting up Server 2012 for a few clients soon, so that will be the benefit of todays research with a new server on a new Hyper-V 2012 standard (I hope).

There are several points that I differ from some of you on coming from the SME marketplace…

1./ Connecting the hyper-v to a domain seems silly, when an amount of the population will want to run their domain controller on the virtual platform itself.

2./ It was nice to go back to DOS for a little while, but too many hardware management features are more time consuming & mistake prone without the GUI’s. (Diskpart & I dis-agreed on which disk was which). We all cost too much per hour to not have clean & accurate tools at our disposal.

3./ Powershell reminds me a lot of the Cisco routers with the CLI. It is definitely less resource intensive, but far too little confirmation of the effects. And another thing to learn that may well become superceded by a GUI. After all, Windows itself superceded DOS. Honestly, if I wanted to go through the needed education to learn how to drive powershell & half effective tools, then I’d be better going back to CentOS & virtualising from there. (That’s quirky too )

4./ I’m also not sure about matching Windows Domain/Workgroup credentials to connect from a management computer. If indeed you want to be able to manage the domain controller host from a workstation, then you need a separate user account & workgroup, or a separate computer if the domain controller VM has failed.

For what it’s worth, I quite liked the 5nine Manager for Hyper-V 3.4. It is useful to have a file manager during the learning curve (even if I couldn’t see anything but drive c:). Corefig 1.1 is also a great example of the GUI confirmations that I find comforting for confirming states & effects of actions. 2Tware convert VHD was quite handy to go from VMDK to VHD to get a machine working.

I reckon if Microsoft gave us back the Control panel & explorer, there’d be a lot more of us using Hyper-V 2012 free. That of course, then generates moves up the ladder to the paid products. VMWare isn’t under any real threat yet.

cheers guys & girls.

I’ve actually heard quite the opposite. Of course I guess it depends what circles you run in.

“It is worth noting that the Windows Runtime stack is by no means entirely incompatible with what has gone before. It still uses the Windows API, although parts are not available for security reasons, and for non-visual code much of the .NET Framework works as before.”

In reality most of the XAML is the same as in Windows Phone too, although not 100%, so skills do transfer pretty well. The biggest difference is in how namespaces are declared and what namespaces visual elements belong to, so every single XAML file needs to be tweaked which means 2 versions of each, but the tweaks themselves are fairly easy.

You’ll generally be creating a different UI for Windows 8 versus Windows Phone anyway, so you’ll most likely have 2 separate XAML files already.

I’m a loooong time delphi dev but moved over to using XCode/ObjC about 4 years ago. I still occassionally use and love Delphi but very few Delphi devs I worked with in the 90s still use it. They all moved onto something else.

The challenge isn’t just from IDEs its also from web frameworks like JQuery Mobile which allow multi-platform development and are completely free. With the advent of HTML5 and packaging solutions like phonegap its quite feasible to build feature rich apps fairly simply and deploy to *all* platforms, not just iOS.

I would echo the sentiments that unless you have a large legacy of Delphi code and/or your headcount contains experienced Delphi devs there is no reason to use it for iOS development. Anyway you still need a mac for code-signing and deploying an app to the appstore anyway!

Gary

Are you going to accuse everybody who uses your substandard products of being a “Troll”.

You just need to face the facts that App Studio is not a serious enough development environment for professional development and for professional apps. It is fine for amateurs who want to produce Mickey Mouse apps. The latter are willing to suffer the numerous bugs, appalling documentation and general failings of your software, although I suspect not at $99.

What you need to do is quite simple. Just listen to your users and find out why so many of them are displeased with what you are charging $99 for, rather than rubbish them and proudly state that you banned them from your forum.

Recently, you issued a 3.0 update, which fixes many bugs and shortcomings of the 2.00 software yet you have the nerve to charge an additional $49 for the privilege of having an update which fixes the fundamental shortcomings that simply should not have been present in the previous version.

This is how you lose customers.

So, once again, I am not a “Troll”, as you like to mislead people about. I am an honest user, who paid good money for a substandard software package. I am out of pocket by $99 and was driven nearly insane by your software.

I have no doubt that you will eventually get it right, perhaps in several more years. NSBasic App Studio simply is not a viable option at this time. It cost me and my team many hundreds of frustrated hours due to fundamental bugs and appalling documentation.

Tim