karstenj
Check me out on the web at IRhetoric - Karsten Januszewski.
@irhetoric
Visual Studio Achievements
Karsten Januszewski is, at heart, a developer. He's been writing code since he was 12 years old and been making a living as a software engineer for the last 15 years, with Microsoft for the last 9 years. He's interested in a variety of topics and technologies, ranging from microformats to metaphysics.He is the lead developer on the following Mix Online projects: Oomph, Glimmer, Flotzam, Incarnate, The Archivist, and The Archivist Desktop. Feel free to contact him with regard to any of those projects.
Visual Studio Achievements FAQ
Feb 02, 2012 at 2:13 PM@djcohen66 - yes, we are aware of this issue and are currently investigating.
Announcing Visual Studio Achievements Beta
Feb 02, 2012 at 2:11 PMVersion 1.2 (uploaded 2/2/2012) should address the experience where you were able to install the extension and VS notified you that you earned achievements, but then your profile was never updated on Channel9.There's no reason to upgrade to this build otherwise. We believe many people reporting issues with proxies will be fixed by this build.
In specific, some proxies were sending a Expect: 100-Continue header from the HttpWebRequest class, which the server wasn't prepared to handle. The fix was to set the static System.Net.ServicePointManager.Expect100Continue property to false.
Also, when you upgrade your extension, if you get a certificate mismatch error, install this hotfix: http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=38654, which will address updating this extension and any other extensions. If you don't want to install the hot fix, you can manually uninstall the extension and then reinstall with the new version.If you are still having issues with your proxy server and this build doesn't solve your problems, please post here and we will continue to investigate the proxy problem.
Visual Studio Achievements FAQ
Jan 27, 2012 at 11:16 AM@WoocasH - Unfortunately no.
Announcing Visual Studio Achievements Beta
Jan 27, 2012 at 11:15 AMYes, we've logged this but about the locked files and are currently investigating...
Visual Studio Achievements Widget
Jan 26, 2012 at 1:19 PMIf you are using this widget, please let us know! We'd love to highlight implementations out on the web...
Visual Studio Achievements FAQ
Jan 25, 2012 at 1:57 PM@blackspy -- All the achievements can be unlocked; sometimes unlocking them can be a bit tricky. It's all part of the game!
Visual Studio Achievements FAQ
Jan 25, 2012 at 1:56 PM@Fabulous_Fadz -- The offline scenario should work and your achievements earned offline will get updated on the server once you are online. Are you not seeing that?
Announcing Visual Studio Achievements Beta
Jan 24, 2012 at 12:20 PMWe just released version 1.1 of the Visual Studio Achievements Extension which addresses the issue of users with an underscore in their Channel9 username. If your username doesn't have an underscore, there is no need to upgrade.
If you installed version 1.0 of the extension and registered with a username that had an underscore, you will need to take the following steps.
1. Go to Tools --> Extension Manager...
2. Click Updates and update the Visual Studio Achievements Extension
3. Restart Visual Studio
4. Go to Tools --> Options --> VS Achievements and click the Change User button
5. Log in and authorize the app
Follow these steps in this exact order and you should be good to go!
FxCop For VS Achievements
Jan 23, 2012 at 4:32 PMNote that it must be FxCop 10.0. So if you installed FxCop 1.36 which comes with Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1 Version 7.0, it won't work. It must be the FxCop that comes with Microsoft Windows SDK for Windows 7 and .NET Framework 4 Version 7.1.
Additionally, if you install FxCop 10.0 somewhere other than the default location ("Program Files"), the extension won't find it. We've logged this as a bug which we will address in a future release of the extension.
FxCop For VS Achievements
Jan 20, 2012 at 10:43 AMThanks everyone for telling us about this; we've logged the issue and are currently investigating.
See more comments…