I’ve always been interested in developing for Windows 8 but I also felt that the SDK is still in its infancy. If you look at ASP.NET now and try to partially compare it to Windows 8’s SDK it’s clear than Microsoft still has a long road ahead to make it simpler and faster to develop for.
That being said, I’m currently playing around with the SDK trying to develop an app for a project I’m working on at work. I’d love to be able to test what I have so far on a Windows 8 tablet though. I’m not sure if it’s possible to, for example, deploy the app to a Surface RT/Pro for testing purposes. I’d hate to think that I can only test my Windows 8 app on my non-touch laptop.
I really hope XAML’s syntax gets a lot cleaner in future versions. Currently it just looks like a big pile of confusing XML mess (to the untrained eye I guess).
There isn’t any. Microsoft has Visual Studio for developing all sorts of applications including Windows Phone apps and it is simple, elegant and a 10 year old could probably do it. And Apple has their own Coco development IDE for creating Mac and iOS applications.
What about BlackBerry? Why don’t they have a complete development environment?
It’s always a massive inconvenience to me when I have to download, unpack, and install several SDKs and JDKs and configure them just to be able to create a simple ‘Hello World’ java application. But BlackBerry has a platform running on millions of devices and even an upcoming new platform (BlackBerry 10) that’s suppose to change the industry. Yet, they still haven’t got a single and complete development environment.
How is that suppose to attract developers? If anything, it will just continue to differ them to a simpler solution that doesn’t require a master’s degree to start creating apps.
If you’re getting the following error:
The version of the .NET Framework launch condition ‘.NET Framework 4’ does not match the selected .NET Framework bootstrapper package.
..chances are your .NET Framework prerequisite under the setup project doesn’t match one or more of the projects added to the setup project.
Check which .NET Framework you have selected as a prerequisite and if it matches all projects added to the setup package. If that still doesn’t remove the warning, select the setup project, click on the “Launch Conditions Editor” button on the Solution Explorer toolbar, select the “.NET Framework” (probably underlined with a red squiggly line) and check the Properties window to see if the Framework selection in the dropdown also matches all projects.
See this blog post for more information on the Conditions Editor.
I experienced an issue with Visual Studio 2008 Team Explorer where I couldn’t remap a certain local solution to a solution in TFS due to workspace conflicts. I removed all workspaces used in the VS2008 and tried to remap again but with no luck. Apparently some of the mapping information is stored in TFS cache on the guest machine itself.
Thanks to Dennis van de Laar and his blog post, I found the path to the cached information and deleted them. Remapping the solution worked flawlessly after that.
You can find the cached information in: C:\Documents and Settings\[user]\Local Settings\Application Data\Microsoft\Team Foundation\2.0\Cache\
via Dennis van de Laar