Dear,
I cloned the entity framework git repository to get debugging support which I need to analyse some problems during my development. After cloning the repository I worked through
https://entityframework.codeplex.com/wikipage?title=Getting%20and%20Building%20EF%20Runtime and
https://entityframework.codeplex.com/wikipage?title=Getting%20and%20Building%20EF%20Tools
The dlls, pdbs and xml files are created as expected (some unit tests failed because of naming conventions with my sql server instance but I do not need to run the unit tests), but the nuget package and the msi installer is not created for me.
Because I am not reliant on nuget, this is not a problem for me. But i am using code first migrations, which needs the Enable-Migrations, Add-Migrations and Update-Database commands to be available on the nuget package manager console (I found no solution to run this comments from a c# application).
The libraries I can use normally without the msi and without the nuget package, but actually I haven't any idea on how to make the code first migrations run for me. Could you please advice me on integrate this commands?
Kind regards,
Sebastian.
Comments: Howdy Sebastian, Here are some answers. 1. No, you may reference the dlls directly. The NuGet package just takes care of adding some things to your App or Web.config. It also includes the Package Management Console integration for Code First Migrations. 2. The typical way to do this with NuGet packages is to use the SymbolSource.org integration. We've tried to provide this special symbols package, but there were issues with symbolsource we weren't ever able to get resolved. I believe we still have a workitem to follow up on this. As an alternative, you can manually copy the pdbs next to the dlls under your project's packages/EntityFramework.*/lib directory. 3. Yes. Please see [my answer to a StackOverflow question of the same](http://stackoverflow.com/a/20382226/475031). You can also attach the debugger to the commands by attaching to devenv.exe--the Visual Studio instance in which you'll be running the commands. 4. I don't know that I have any specific answer for this. Debugging is a good way to understand what EF is doing behind the scenes. If you find any unexpected behavior, please file a bug and we'd be happy to investigate. Let me know if I can provide any additional help. -Brice
I cloned the entity framework git repository to get debugging support which I need to analyse some problems during my development. After cloning the repository I worked through
https://entityframework.codeplex.com/wikipage?title=Getting%20and%20Building%20EF%20Runtime and
https://entityframework.codeplex.com/wikipage?title=Getting%20and%20Building%20EF%20Tools
The dlls, pdbs and xml files are created as expected (some unit tests failed because of naming conventions with my sql server instance but I do not need to run the unit tests), but the nuget package and the msi installer is not created for me.
Because I am not reliant on nuget, this is not a problem for me. But i am using code first migrations, which needs the Enable-Migrations, Add-Migrations and Update-Database commands to be available on the nuget package manager console (I found no solution to run this comments from a c# application).
The libraries I can use normally without the msi and without the nuget package, but actually I haven't any idea on how to make the code first migrations run for me. Could you please advice me on integrate this commands?
Kind regards,
Sebastian.
Comments: Howdy Sebastian, Here are some answers. 1. No, you may reference the dlls directly. The NuGet package just takes care of adding some things to your App or Web.config. It also includes the Package Management Console integration for Code First Migrations. 2. The typical way to do this with NuGet packages is to use the SymbolSource.org integration. We've tried to provide this special symbols package, but there were issues with symbolsource we weren't ever able to get resolved. I believe we still have a workitem to follow up on this. As an alternative, you can manually copy the pdbs next to the dlls under your project's packages/EntityFramework.*/lib directory. 3. Yes. Please see [my answer to a StackOverflow question of the same](http://stackoverflow.com/a/20382226/475031). You can also attach the debugger to the commands by attaching to devenv.exe--the Visual Studio instance in which you'll be running the commands. 4. I don't know that I have any specific answer for this. Debugging is a good way to understand what EF is doing behind the scenes. If you find any unexpected behavior, please file a bug and we'd be happy to investigate. Let me know if I can provide any additional help. -Brice