VS2013 Update5

31.12.2015 установил обновление Update 5

Using Build Events in Visual Studio to Make Life Easier

http://jeremybytes.blogspot.ru/2014/02/using-build-events-in-visual-studio-to.html

Visual Studio Connect Feedback

https://connect.microsoft.com/VisualStudio/

MVC5 Add External dll class library (Add External reference as Project reference) to Web Mvc5 Project

https://connect.microsoft.com/VisualStudio/feedback/details/809839/visual-studio-2013-pro-add-view-does-not-show-a-referenced-data-access-class-library-model-in-the-model-class-drop-down-list

https://msdn.microsoft.com/en-us/library/f3st0d45(v=vs.140).aspx

Vusual Studio Updates

http://support.microsoft.com/kb/2994375

VS

1, VS 2013 Eng - без ключа
2. VS 2013 Eng - с ключом
3. VS 2013 Rus - с ключом

VS 2013 Web API Add Controller Dialogs - How to add Model and Context from Referenced Library?

Copy from Here

http://stackoverflow.com/questions/20976962/vs-2013-web-api-add-controller-dialogs-how-to-add-model-and-context-from-refer

0down votefavorite

Adding a controller in a Web API project works very well - only if your models and EF data context are in the same assembly as the project itself - i.e., located in the project's Models folder. I created all the POCOs and EF data context in a separate library project, created the library, and referenced it from the Web API project. Unfortunately, the dialogs can only see models and data context whose .cs files reside in the project. I've looked at similar questions and somehow, other people's add controller dialogs list their models and data contexts from external (referenced) libraries (then they have a different problem, which my problem isn't getting to (yet)). Is there such a setting (in the IDE or web.config) that I need to specify so that these add controller dialogs will see my library's classes? visual-studio entity-framework dll poco datacontext share|improve this question asked Jan 7 at 16:36 Mickael Caruso 9011414

add comment

1 Answer

activeoldestvotes

up vote0down vote

So far, I've come up with a "dirty" workaround, which I'm not very satisfied, though it works: Create a dummy class under /Models with arbitrary properties – but one of them has to be int Id. Go through the add controller dialogs and choose the dummy model. If you haven’t created a data context, click on New data context. Beware that the dialog will auto-generate the full qualified namespace path of the data context, and that the context name contains a space. Remove it. Click add. Open the auto-generated controller .cs file. Reference your library in this .cs file that contains the model and the context. Find and replace all instances of the dummy class with the actual model’s class name you need. Be careful of plurals. String-replace plurals first, then singular after. Change the dummy context class to the correct data context class.