I was looking into the licensing of Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll, and wasn't comforted by what I found:
http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/32384366-b668-4f18-99eb-9c67f7eef233/ Just in case anyone reads this - I called them, and since the unit testing portion of visual studio is not available as a separate download, it is licensed as part of the Visual Studio product. It can then be distributed under an ISV license -- as though you were buying and distributing Visual Studio. Which by my reading requires a Visual Studio license be present in order to use the assembly. Thus, it's a Bad Idea to have a copy of this in svn, as it (1) allows Express users to use the assembly (and Express users aren't licensed to use this assembly), and (2) allows #Develop and MonoDevelop users to use the assembly (which isn't Visual Studio at all). Thus, do we actually need this assembly? Would it be safe to remove this assembly and instead depend upon NUnit for unit tests (which we're already largely doing anyway)? (I'm particularly interested/concerned as the DbMetal unit tests currently depend upon this assembly, and I don't want to copy the assembly into Mono to use the DbMetal tests within Mono. I can certainly add #if MONO_STRICT logic to the appropriate tests to strip out the QualityTools usage, but before I start adding more conditional logic I thought I'd see if it was needed at all...) Thanks, - Jon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
