The Digital Tool Factory Blog

1. First – backup the __MigrationHistory table in the database
2. Get rid of old migration files
3. add-migration using the usual syntax, but with nothing modified
4. Remove all of the “Create Table”, etc – the migration should look like

public partial class domorenow : DbMigration
{
public override void Up()
{

<code>    }

    public override void Down()
    {

    }
}</code>

6. from there do the update-database -script to generate a sql file
7. then just update-database -verbose
8. All Fixed

Update – I did some more Googleing and found this page

Whereupon it says to

In your Team Explorer panel, click on Home > Projects > New Team Project…

Actually you have to click on Home to do it

but that gives you

Create from there

Due to a variety of circumstances I’m creating new projects with Visual Studio 2017, but using Team Foundation Server 2015 to house the source code – here is the proper sequence (for me) that gets the source code in place properly

1.  Create Team Foundation Server Project using Visual Studio 2015 – note remote origin server
2. Disconnect from VPN (and therefore TFS)
3. Create Solution normally using Visual Studio 2017
4. Do the normal “Add to Source Control” (from the File menu)  (if you do this while connected to the VPN/TFS it will try to force you to save it to TFS (where you can’t create a new project, or see the project you just created) – it will then do all the Git setup normally
5. Reconnect to the VPN
6. In the Team Explorer settings, add the remote origin server location to the “Remotes” section in the Repository settings – don’t forget to use the name “origin” as the name
7. Commit and Push – everything should be working fine.

I’m sure there is a much better way to do this, but this is what works for me.

Recently I was working on a project and noticed that none of my jquery code extension were working in Visual Studio 2015.  After much rending of garments and gnashing of teeth I discovered that the jquery code snippet plug just doesn’t work with jquery 3 – I downgraded to the most recent version of 2.0 and it all worked perfectly.

Recently I was deploying some sites, and got the error “Compiler Error Message: The compiler failed with error code 255.” – which looks like this

after some research the cause of, and solution to was all in the nuget package manager.  I had recently added a new project to the solution and some of the more “stock” nuget packages were out of sync with with the newer packages.  Make sure all of the nuget packages are the same version and your problems will be resolved.

This is non-intuitive, but all you have to do is click in the zoom area – type in the value (in my case 90%) and then click enter, NOT TAB OUT.

That just threw me for ten minutes.

For some reason the otherwise delightful nuget Package FoolProof Validation does not work with modern version of the entity framework – rather, the validation works just fine, but it chokes when you try to update the database with entity framework.

The workaround I found was to validate on a view model – and then translate that viewmodel to the actual model, which is then sent to the database.

For whatever reason you cannot directly deploy (using Visual Studio WebDeploy) to a virtual directory in IIS.  This threw me for a bit until I created both the virtual directory, a separate website, and pointed them both to the same directory.  Then you just deploy to the otherwise unused website, and your web application shows up in your virtual directory