EF migration failing

[pgmolloy]

No description provided.

[pgmolloy]

This is happening just using the tutorial I am unable to use EF migrations for 2.0 projects right now. Here's what I receive using the tutorial. My files are same as tutorial. Take a look at the second line being generated "rosoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[0]", where is this coming from.
PM> Update-Database -context 'BloggingContext'
rosoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[0]
Update-Database : Exception calling "Substring" with "1" argument(s): "StartIndex cannot be less than zero.
Parameter name: startIndex"
At line:1 char:1
Update-Database -context 'BloggingContext'

• CategoryInfo : NotSpecified: (:) [Update-Database], MethodInvocationException
• FullyQualifiedErrorId : ArgumentOutOfRangeException,Update-Database

[ajcvickers]

@pgmolloy Can you post a link to the specific tutorial that you are following?

[ajcvickers]

EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.

BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.

[oneandy]

Somewhere in our code, there is a Console output, with ":" in the string.
We are using EF1.1.5, it appears OK with version 2.0.1
This is the broken code.

    public class BloggingContext : DbContext
    {
        public DbSet<Blog> Blogs { get; set; }

        protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        {
            Console.WriteLine(":"); //This is the end of the world.

            optionsBuilder.UseSqlServer(@"Server=;Database=EFGetStarted.ConsoleApp.NewDb;Trusted_Connection=True;");
        }
    }

[ajcvickers]

@oneandy If you are reporting a bug, can you please open a new issue with a full description of the behavior and a runnable project/solution that demonstrates the issue.

[bricelam]

@oneandy That was issue #8163