Comments

Vs RC looks a lot better except for the all caps menus (obviously) but i'm a bit bummed that they only showed the light theme and not the dark theme.. all in due time i guess

@felix9:

it might look alright if it wasnt for that cement gray..

yay, brian

@Lars Kemmann:

But adoption is slow because the finalization of the standard itself if slow. No significant webside can afford to only support one or two of the major browsers. 

I dont have anything against standards, i love 'em. Its the quibbling of the standards bodies that's the problem.clearly if browser vendors resort to custom extensions, the standards arent evolving fast enough.

i agree that we should follow the money, but i dont think microsoft google or apple are the ones controlling this as much as it is the millions of app/site developers out there. users dont care about any of this technical stuff, they dont care about standards, or what browser they use, they dont care if all the web is one native app or their os is just one big browser, they only care about their personal user experience on the device they happen to use.

Allthough it might be alot of trouble for developers to develop highly optimized native apps for all the diffrent platforms, it will only be "uneconomical" if they dont provide a better user experience by doign this than using some other method.

it will be interesting if the webstack will ever be able to provide such a method i dont think it is now though, and i think its going to take a while if it ever happens. Right now html+js has a huge competetive edge on web (its the only option actually) but once apps start breaking out of the browser this will no longer be the case. interesting times i say

What's going to be interesting is just how well the html+js stack will do once it has any kind of competition on equal terms as a programming model, as will be the case in windows 8

Personally i dont think native(or formfactor/platform specific i should say) apps are going away anytime soon. HOWEVER i do think that those apps could very well be written in html+js. but they will be platform specific, again as is the case in windows 8, still requring developers to develop for each platform.

Standards bodies are just to darn slow, and they always will be because of the simple fact that they are comprised of humans trying to reach an agreement.

Even if they where fast enough, browser vendors are to slow to implement the standards.. even css3/html4  is not entirly consistent, even between ff and chrome, not to mention mobile.. (input fields anyone?)

@briankel:

Thats really odd, it has never shown up for me at home or at the two diffrent companies ive worked at for the past five years and i know for a fact wsus was not enabled on two of these places.. Maybe its a regional thing, Sweden still get Bing beta(!!) unless you manually go in and change the language to en-us

anywhoo, its a great feature! as long as everyone has sp1

1 day ago, rogreen wrote

@aL_: You can open a VS 2010 project in VS 11 without having to convert it even if you don't have SP1. SP1 is required if you want to make changes in VS 11 and then open the project again in VS 2010.
I'm not sure I understand why having to manually download SP1 makes any feature useless.

well yeah... but thats not really backwards compability though is it.. The whole point is to be able to go back and forth between VS2010 and VS11.

Not having VS auto update itself nor via windows update [and i just checked again on several coworkers machines and SP1 does not show up on win update, even if external updates are enabled] makes the backwards compat useless in practice since anyone actually using vs11 will have to go around, manually convincing every other developer to manually update, a process that can take something like 30-45 minutes. That just not going to happen..

This is a great feature, its just a shame the lack of properly woking update infrastructure in vs2010 limits its use in small teams and makes it impossible to use in larger teams.

i was so excided when i heard about this feature, how ever i was even more dissapointed when it didnt actually work

To be more specific, it doesnt work if the vs2010 users have not installed SP1, and sadly(and inexplicably) this vs2010 sp1 is not available though windows update, even if you go through the help menu in vs and ask it to look for updates, its not found.... you have to download it manually

its so so sad that this great feature is made useless by the fact that vs2010 is not automatically updated to sp1 :/

cant see it in he marketplace yet  /cry

really cool to see these kinds of investments in the full .net framework

maybe a single .net framework is not just a pipedream