65 Kicks

Microsoft cracking down on community extensions (lovethedot.blogspot.com)

published 1 year, 7 months ago, submitted by RagoczyRagoczy(650) 1 year, 7 months ago

Microsoft released a tool called Microsoft Source Analyzer, or StyleCop. It analyzes source code for standards violations. It's a 1.0 release, so it doesn't do some things ... like have a published API for custom rules or MSBuild integration. So the community dug in and figured out how to do these things and now MS is firing off license-violation emails. Don't they get it? The community wants to use the product, but it's too limited ... these extensions help make it better.

5 comments | category: | Views: 503

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
gavinjoycegavinjoyce(25.7k) - camalotcamalot(630) - jongallowayjongalloway(4175) - crpietschmanncrpietschmann(11.1k) - drmohundrodrmohundro(279) - entrodusentrodus(10) - cdjacocdjaco(5) - joycscjoycsc(1285) - bokiboki(55) - pmbrownpmbrown(0) - BognitBognit(1770) - superghostsuperghost(2260) - ejsmithejsmith(0) - ercuercu(15) - filipffilipf(5) - drugarcedrugarce(590) - mdoppmdopp(850) - senfosenfo(870) - AmrElsehemyAmrElsehemy(2580) - offwhiteoffwhite(975) - AnastasiosyalAnastasiosyal(955) - NathanBaulchNathanBaulch(0) - RemanReman(1970) - terrbleterrble(1665) - ashmindashmind(765) - bennagebennage(1140) - fquednaufquednau(395) - powerrushpowerrush(3754) - aquinasaquinas(20) - kayoskayos(880) - Zero3Zero3(0) - jdschwarjdschwar(365) - jazzman007jazzman007(170) - malovicnmalovicn(1450) - TroyMGTroyMG(2670) - DannyDouglassDannyDouglass(1200) - dist0rti0ndist0rti0n(125) - adminjewadminjew(1490) - dcrennadcrenna(1355) - darrenstokesdarrenstokes(300) - keithelderkeithelder(445) - nsoonhuinsoonhui(1805) - AmaranthAmaranth(125) - sjclark76sjclark76(155) - jemtsjemts(370) - blacksauronblacksauron(0) - dstar01dstar01(0) - samuel_d_jacksamuel_d_jack(415) - goatweedgoatweed(0) - sidaroksidarok(1715) - RipRynessRipRyness(375) - mattman206mattman206(305) - AlexCuseAlexCuse(325) - spoulsonspoulson(255) - RagoczyRagoczy(650) - QuantumBitDesignsQuantumBitDesigns(315) - YuraYura(995) - martinbmartinb(0) - briangrafbriangraf(0) - rayhenryrayhenry(100) - HappyCodeHappyCode(0) - atlasatlas(15) - taylorparsonstaylorparsons(0) - sangam100sangam100(295) - oglasioglasi(0)

Comments:

posted by gavinjoycegavinjoyce(25.7k) 1 year, 7 months ago

Two steps forward, one step back.

posted by duckieduckie(150) 1 year, 7 months ago

Easy now. There is a long way from some paper-pusher to the folks making the decisions. I am sure something will happens the next few days.

posted by bennagebennage(1140) 1 year, 7 months ago

:( Sounds eerily like the TestDriven.NET story...

posted by myspacelayoutsmyspacelayouts(0) 1 year, 6 months ago

so stupid move. :(

posted by RagoczyRagoczy(650) 1 year, 6 months ago

There's an update to this story with links to clarifications and responses by Microsoft (http://www.dotnetkicks.com/csharp/Update_to_Microsoft_cracking_down_on_community_extensions). Also, the original, redacted blog post that was removed "at Microsoft's request" is now back up. I hope everyone who formed an opinion based on the original story will give their responses and opinions a fair hearing.

information Login or create an account to comment on this story
View upcoming stories
Submit a story
How else can I help?
Add our feeds to your site

Most Active Users