4 ms·
Moreover, their business unit's licensing/pricing team are chasing your code forever to suck more margins from its use. While developing with MS technologies,
by diminish 13y ago
Moreover, their business unit's licensing/pricing team are chasing your code forever to suck more margins from its use.
While developing with MS technologies, you must accompany any code, tests and documentation with a "My License" folder with "licensing.cs" files to calculate, the implied licensing costs of each piece of code you develop along with all required MS components down to the metal. Finally, you must make sure the relevant "My License/licXX.cs" gets updated with changing licensing policies.
Next to your developers, designers you must staff an MS certified licensing specialist, or for larger projects a License team with a director level position to analyze, plan, design, test, negotiate and pay licensing costs.
- yulaow 13y agoI never ever ever read anything about it. Can you link some information related? Because googling it I can't find anything
- WickyNilliams 13y agoHaving worked on many enterprise .NET projects I can assure you this is not true, at least in the general case. Licensing is definitely a complex beast but I have never heard of, or followed, this requirement
- codelap 13y agoYea, this is complete bollocks. Not a word of it is true. You may have a shitty thing in your corp that forced you to do this, but that has nothing to do with Microsoft.
- alkonaut 13y agoThis is satire. Calm down.
- diminish 13y agothanks for getting the satire :-) few years back i used to work for mankind's largest IT project leading a C# team to develop certain missing parts. Licensing implications for each piece of idea were so immense, we needed to keep architectural decision inline with licensing plans.