search

jbubriski / ST4bby

A POCO generator that doesn't rely on the Entity Framework.
MIT License
18 stars 8 forks source link

Reserach usability issues with SMO. #6

Closed jbubriski closed 12 years ago

jbubriski commented 12 years ago

Mainly, how to get SMO (SQL Server Management Objects) pulled in automatically, or is there another library?

Can we include SMO? Is there a Nuget package for SMO? Roll our own SQL?

Yup.

codeimpossible commented 12 years ago

Maybe we could manage the dependency by just putting our project here on Nuget ourselves with the SMOOOOOO dlls already included?

jbubriski commented 12 years ago

Yeah, definitely, if we're allowed to redistribute.

jbubriski commented 12 years ago

This MSDN blog post says we can redistribute, but the information is for older versions: http://blogs.msdn.com/b/mwories/archive/2005/05/02/smofaq.aspx

This page on the MSDN doesn't mention anything about restrictions, but does suggest that we're able to do it: http://msdn.microsoft.com/en-us/library/ff713979.aspx

Found a StackOverflow question on the topic, but it doesn't have any additional info: http://stackoverflow.com/questions/8593116/can-i-distribute-and-install-sql-server-server-management-objects-with-my-applic

codeimpossible commented 12 years ago

SMOOOOO SMOOOOO

jbubriski commented 12 years ago

DEATH BY SMOO SMOOOOOO! (Not snoo snoo)

jbubriski commented 12 years ago

We tested this out and the SMO files are put into the GAC when they're installed. So we don't need to worry about physically including them or directly referencing with ST4bby.