<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/platform.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d33142127\x26blogName\x3dfishyweb\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dBLUE\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttps://fishyweb.blogspot.com/search\x26blogLocale\x3den_US\x26v\x3d2\x26homepageUrl\x3dhttp://fishyweb.blogspot.com/\x26vt\x3d4851815010354999608', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Msdn Reader Up & Running finally!

Side effects!

Call it blind luck - I had changed the IE proxy settings from VS to enable the PInvoke.net plugin to work properly from within VS.

And as a welcome, side effect - the MSDN Reader started working as well. All the while, i've been breaking my heads to get the MSDN reader work thru the proxy settings!

So, MSDN Reader *does* take its proxy settings from the IE settings. good!
Voila!
:)

You can leave your response or bookmark this post to del.icio.us by using the links below.
Comment | Bookmark | Go to end