Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Discussions

DouglasH DouglasH Just Causual
  • What is missing from the CLR  (2010 update)??

    Charles said:
    Sven Groot said:
    *snip*

    Yes. The editor is broken. Let me manually fix it...

    C

    EDIT: Duncan has been informed. Apparently, the editor creates relative path strings out of URL input data: removes the protocol and domain from the URL...

    Thanks Charles that was an interesting interview.  Abstract? interfaces sound very interesting. sort of a poor mans mixin??. But something that is sorely needed in OO either way as Interfaces versioning currently is a Pain.

    Isolation and message passing will be interesting in how it is integrated into the current languages.  I know Axum is playing with it in a non class based way, haven't started playing with it yet. Been playing more with F#.

    Exoteric, that may be the case, I know IronRuby have implemented mixins.  But is that because of DLR, I know there was a talk at last years Lang.net where mixins were implemented also for C# but they were asking for language support.  Mixins solve a lot of the multiple inheritance issues without alot of the issues.  (Ruby is a single inheritance language also).

    Continuations??

    thanks Douglas

     

  • What is missing from the CLR  (2010 update)??

    http://channel9.msdn.com/posts/TheChannel9Team/Brad-Abrams-What-is-missing-from-the-CLR/

    can we revisit this topic from 2004??

    since that was way back before whidbey was released.  now what is missing from the CLR updated to 2010 would be an interesting revisit.

    Continuations, and Mixins would be a good discussion. 

    Thanks Douglas

  • Sheila gets a HP

    Evil SEO said:
    "No more so than your "it doesn't on work on my machine; wait actually it's not my machine, I have this friend... ok I admit it I read it on the Internet" nonsense."

    It's widely known that many companies didn't release 64bit drivers for their hardware and that the older drivers for XP x64 have hard times working on Vista x64 because Microsoft requires signed certificates while on Vista 32bit you can run most XP drivers, including video and sound drivers without issues because no certificates are required, no need to ask to friends or look on teh interwebs, everybody knows that a lot of older hardware doesn't work on 64bit windows systems because hardware companies couldn't care less to port, test, and pay for WHQL certification for discontinued hardware, knowing that if they did then you'd have no reasons to buy newer hardware from them.

    "Yes, there is short term grief to be had with going off the deep and supporting 64 bit properly. Apple will have to pay that price sometime down the road. And honestly, if you want to blame people for buggy or missing 64 bit drivers, blame the people who write those drivers, not MS."

    Hardware makers aren't supposed to support their products forever so no need to blame them unless they're Logitech, Creative, Canon or Dlink that discontinue their products way too quickly. On OS X you can run 64bit applications and use the extra memory without being forced to install 64bit drivers so there are no hardware backward compatibility issues, Apple is already requiring hardware makers to release driver packages with both 32bit and 64bit drivers inside so when Apple will permanently drop the 32bit kernel in a few years you'll probably have all your 64bit drivers already there (and already tested by people who tried using Leopard x64) without having to desperately go looking for modded drivers or drivers for similar hardware that could work like you have to do on Windows. It's a much better approach than Microsoft's that moved everything to 64bit caring only about applications but not about drivers and killed backward compatibility with XP 64bit drivers by accepting only signed drivers, on OS X you get all of the 64bit advantages without being required to dump any of your older incompatible hardware.
    "It's widely known that many companies didn't release 64bit drivers for their hardware and that the older drivers for XP x64 have hard times working on Vista x64 because Microsoft requires signed certificates while on Vista 32bit you can run most XP drivers, including video and sound drivers without issues because no certificates are required, no need to ask to friends or look on teh interwebs, everybody knows that a lot of older hardware doesn't work on 64bit windows systems because hardware companies couldn't care less to port, test, and pay for WHQL certification for discontinued hardware, knowing that if they did then you'd have no reasons to buy newer hardware from them."

    But Evil, are you not compareing apples to oranges here.  Apple has a draconian control on what hardware is available on their hardware.

    Microsoft is not a hardware company (for the most part), when we are talking a Microsoft PC we are talking an OEM that chooses to use MS OS and usually hand picks a group of hardware for that system.  Although there is that idea of expansion of which a Microsoft PC has millions of more choices than the Apple PC.

    Mentioning the point of 32 bit drivers in comparison to signed 64 bit drivers. It is a way to get control on drivers. Since in the 32 bit unsigned world 80% of BSOD's and general unstability were caused by those drivers without controls.

    So the comparison would be. in the Apple world where a hardware Vendor has to to through apple before they can sell hardware for apple systems. is true for 32 bit and the 64 bit world.

    in the microsoft world that wasn't true until the 64bit world at the consumer level. 

    I personally was disappointed that MS didn't take the high ground and force 32 bit signed drivers also.

    Douglas

  • Sheila gets a HP

    Sven Groot said:
    Evil SEO said:
    *snip*
    Fair enough. On my system, most games suffer about a 20-40% loss in performance in DX10 mode compared to DX9 mode, but this is likely due to my video card.

    It's true that pure 64 bit mode isn't going to help straight computation much. Sure, the extra registers will make some difference, but you won't see it except in some very specific situations.

    However, Paolo's original assertion was that 32/64 bit context switches on MacOS X causes overhead. I don't really see how comparing 64 bit and 32 bit Windows to each other has any relevance to that at all.
    more than likely is that it isn't a true dx10 game from the ground up. but a dx9 game with dx10 features shoe horned in.

    Douglas

  • PDC pages

    If you go to the main page, http://channel9.msdn.com/pdc2008/  if you select the wpf the videos for windows 7 pull up.  does that on alot of links.  


    Give me a bit of time and I can tell you all of them.  also when the windows 7 vids come up if you try to go to the second page of videos non show up and it shows 1 to ? 

    all these links go to the window 7 page and same issue.

    on that page, ad platform, azure, ccr, dynamics, entity framework, expression, hpc, identity, iis, Internet explorer, languages, linq, live framework, live mesh, live services, office, oslo, parallelism, powershell, research, sharepoint, silverlight, sql server, 

  • PDC pages

    the pdc2008 pages are severly broken.  while talking about them is there anyway to get the Slides back ??

    thanks Douglas

  • How retarted it is that Win7 setup still doesn't provide...

    OnlyJack said:
    Yggdrasil said:
    *snip*
    I wish I knew before that posts titles can't be edited since this one was my first post. I had to cut&paste the post and rewrite the title at least four times because I was keeping getting a nice "The server method AddPost failed." msgbox all the time.

    I think the issue is in the videocard itself, I've read of some people flashing other video bioses to stop the issue however if all you need to make it stop is specify through msconfig boot options how much RAM and how many processors/cores your CPU has it's definitely either a driver issue or the OS reporting wrong values to the video driver. What is known is that it's not just me having the issue, there are at least 40 pages about the problem on AMD forums (that I linked in my 2nd post) and also tweaked Catalyst drivers like DNA's are including a patch for the issue.

    That said, it's still nonsense for the windows setup to lack an option to disable third-party drivers loading during the install because Microsoft cannot ensure that all the included OEM drivers in the windows install disc will work correctly on any PC configuration. For instance, when I installed vista for the first time, the install was BSODding too due to the broken JMicron driver included in the disc and I wasn't the only one with that issue, just look at some of the titles of these google results. In that case I could get rid of the BSOD by selecting IDE mode (not available on all BIOSes) or by loading a newer JMicron the driver from the setup but as said this can't be done with all drivers because only few hardware manufacturers give you those pretty ZIP files with just the "naked" driver inside requiring no extra useless software or setups to work that can be loaded in the windows setup.
    OnlyJack,

    Well gotcha taken care of as I am having the issue, and yes from my research it has been going on for quite awhile now.  Although I did just build this system all MTI amd chipset and ati vid card.

    Funny thing is that it also occurs with the onboard vid

    I would hope from the near daily BSODs that I am getting and reporting back to MS in win7 will provide enough info that they can finally fix this stupid thing.


    Douglash

  • Any hints yet on VS 2010/.net 4 CTP or BETA release date?

    nothing definitive.  but rumors are around Mix timeframe.  Rumors are early views of silverlight 3 and blend 3 also.

    ymmv
    Douglash

  • Longhorn RESET caused by .Net?

    I would say it is a little short sighted to say the reset occured because of .net. 

    It was more a dependacy issue than a .net issue.  And a moving dependacy issue, things broke build to build because the underlying dependacy changed build to build. 

    Add to that the Sasser, Blaster and other worm attacks and the obvious fact that updates were not being applied. 

    Looking back, the Reset was caused more precisely by the Blaster Worm attack which forced MS to basically significantly rewrite and recompile portions of XP. portions of which were in 2k3. That undertaking took significant Manpower from the OS group to the support group at MS. Effectly stopping development on Vista.

    The aftermath was that when sp2 was complete, the resulting code base synced with the 2k3 code base. And a Strong advancement in security from the base started in earnest. Part of the Security review was the new check in policy which was to ensure that the module was working before checked into main.  so the concept was scaled back.  also due to populiar demand some of the features were then abstracted and brought down level.  (avalon being the biggest one) 

    of course this IMHO>

    Douglas

  • OneCare Rocks!

    Unfortantly OneCare is also a dead product. 

    Official support to end in June.

    Douglas