Is there a way to update Entity Framework entities after the initial code generation.
The scenario is a MySQL application was developed in Visual Studio Community 2013 and the "code first from an existing database" wizard was employed. At a later time, a new table was added to the database. I used MySQL Workbench to add the table. At this point, how can the entities be updated to include the database as it now stands?
Our first step in EF7 is to provide a similar reverse engineer process to what’s available in EF6.x – and that is most likely what will be available for the initial release. We do also have some ideas around pulling in incremental updates to the model without overwriting any customization to previously generated code.
That's from this 2014 October post from Microsoft
It seems then, that incremental reverse engineering is not an EF6 capability but they have "ideas" in this area for EF7.
Related
Looking for documentation about moving only a subset of contents from a TFS 2018 server in certain domain and hardware to another TFS 2018 server in another domain and hardware.
More Details :
It is possible to follow general instructions for migrating a tfs to another server/domain, but we need only a subset of the contents i.e. contents for specific team projects in the single default collection that we have. The existing documentation in microsoft docs relates only to all the contents as a whole. We'd thus also like to assess whats recommended : migrate all and delete relevant contents on target or migrate only relevant contents from source to destination. Contents include : code, work items, Build & Release, all history, etc...
There's no way split individual projects out of a team project collection without resorting to third-party integration tools and suffering from a lot of pain.
The best solution is to clone the team project collection using the standard process, migrate it, then delete what you don't want.
I am using TFS 2013 update 4:
Scenario:
Add a new iteration from the administration page of a project.
Go to the project Dashboard create a new work item.
Newly created ierations and areas are not shown in the relative dropdowns.
Steps taken:
Checked the server for errors in the event viewer, no issues.
Check the 'Visual Studio Team foundation Job Agent' running with no issues under the TFS admin user.
The newly created iteration exists in the collection database table 'tbl_nodes' and in the 'TFS_Warehouse' Database.
Checked the Jobs on the database and forced them to start, did not solve it.
What I was not able to do is figure out which table exactly the TFS is querying the nodes from, afterall the Stored procedures are encrypted.
Amemdment:
**the newly created iterations exist in the 'tbl_nodes' but does not exist in 'TreeNodes' table.
Since newly created iterations and areas are both in database. Try to restart Team Foundation Background Job Agent service to force synchronization in TFS server.
If it's still not help, give a try with rebooting the server, which may do the trick. You can also take a look Mark's solution in this similar issue Newly created TFS 2010 iteration not visible
I am currently trying to solve an issue with our current on-premise TFS 2010 Server where I have 2 collections and both of my project collections were set to offline due to some tinkering with trying to upgrade to on-premise TFS 2015.
Whenever I try to activate the desired collection, I am getting the following error:
TF253021:The following team project is duplicated in at least two team
project collections: ProjectName. The collection cannot start while
the duplication exists. You must delete this project from all but one
of the collections before the collection can be started. The project
exists in the following collections: CollectionA, CollectionB.
I also had a look at each of their settings, and apparently the database connection string for both collections are pointing towards the same SQL Server instance and the same database. Both collections also have the same number and names of all team projects too.
I'm thinking of deleting one of the collection and its projects, but I fear that if I do it, it may delete the same collection and settings for the second project collection that I'm trying to set online.
I'm wondering if anybody has encountered this issue and what steps have he/she has done to fix it.
Many thanks!
You've gotten yourself in a remarkable situation, which may need Microsoft support to chime in. Even with creative backups I'd be unsure whether you'd get yourself in an unsupported end-situation.
If you have a backup of the whole situation before you started this experiment, I'd recommend going back to that.
You may find yourself in a catch-22 situation, since TFS 2010 has passed it's support lifecycle. Mentioning it happened while preparing for a TFS 2015 upgrade may convince them.
You can find the contact details here:
https://support.microsoft.com/en-us/contactus/
I have an SQL Server DB that I reverse engineered into my .Net Core App. All is great....until now. I want to introduce Identity. There are plenty of examples on how to do this code first, but not DB First. Has anybody any ideas how I should go about this?
After looking at the Link that #SteveGrenne offered, I did the following.
I created a .net core MVC project and set the project authentication to individual user. I then created a user as per the link. This created and generated the required tables into a default DB. I then scripted the tables and placed these into my live DB. From here on this is where my fix deviated from the suggestion. Using the Scaffold-DbContext command in the nuGet Package manager console I reverse engineered my DB into my desired project. in the Project.json files I then made a reference to the Identity and Cookies packages and changed my Repository Layers that were referencing DbContext to now reference IdentityDbContext
I'm using TFS 2015 on-prem and I'm using the standard SCRUM template. I have 1 Team Project and I'm using the team field to segregate work. I have created a few build definitions and ran a few builds over the last few weeks.
When I installed TFS I did not install or configure Reporting Services straight away as I had planned to do that later. I have since done this and I now have my Tfs_Warehouse which is updating with most things but NOT FactBuildProject or FactBuildDetails. Some of my other facts are pulling over, such as FactCurrentWorkItem and even FactBuildCoverage. I have rebuilt the warehouse in the TFS Admin Console.
As this is a standard process template and standard reports I expect that the required fields should be set to reportable.
How can I get data in my FactBuildProject table and where can I look for issues with it? I'm not sure where to start and I can't find anyone else in the world with a similar problem.
If you are using the new task-based build system, then you are out of luck, since that data is not being propagated to the data warehouse.
Check the comments on this blogpost: http://nakedalm.com/create-a-build-vnext-build-definition-on-vso/