Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / mrahhal/Migrator.EF6 issues and pull requests
#73 - Specify the ProjectName
Issue -
State: open - Opened by ricardosobrado almost 4 years ago
- 1 comment
#72 - Can't create migration after updating to Visual Studio 2019
Issue -
State: closed - Opened by AlonCG almost 5 years ago
- 6 comments
#71 - Your startup project 'BasicConsoleApp' doesn't reference Microsoft.EntityFrameworkCore.Design
Issue -
State: closed - Opened by alpersilistre almost 5 years ago
- 3 comments
#70 - JOIN Tables fails in NetCore 3.0 & EF6.3 with Method syntax (but works with Query...)
Issue -
State: closed - Opened by GuyBenhaim almost 5 years ago
- 4 comments
#69 - Version 3.0.0 doesn't seem to be published
Issue -
State: closed - Opened by Fancy11111 almost 5 years ago
- 3 comments
#68 - .NET Core 3.0 support
Pull Request -
State: closed - Opened by mrahhal about 5 years ago
#67 - Add support for .NET Core 3.0
Issue -
State: closed - Opened by marchy about 5 years ago
- 15 comments
#66 - EF Classic?
Issue -
State: open - Opened by kanadaj over 5 years ago
- 6 comments
#65 - Bump Microsoft.AspNetCore.Mvc from 1.1.2 to 1.1.3 in /samples/WithIdentity
Pull Request -
State: closed - Opened by dependabot[bot] over 5 years ago
- 1 comment
Labels: dependencies
#64 - rror MSB3027: Could not copy "obj\Debug\net47\*.EntityFramework.dll"
Issue -
State: open - Opened by muehan over 5 years ago
- 5 comments
#63 - dotnet ef migrations add [filename]
Issue -
State: open - Opened by neal-payload over 5 years ago
- 2 comments
#62 - Add support for .NET Core 2.2
Issue -
State: closed - Opened by marchy over 5 years ago
- 11 comments
#61 - Your startup project doesn't reference Microsoft.EntityFrameworkCore.Design
Issue -
State: closed - Opened by DOTang about 6 years ago
- 6 comments
#60 - Incorrect ResourceManager path for RESX
Issue -
State: open - Opened by jsgoupil about 6 years ago
- 7 comments
#59 - Handle adding resx file as EmbeddedResource when csproj EnableDefaultEmbeddedResourceItems is false
Issue -
State: open - Opened by ryangribble about 6 years ago
- 1 comment
Labels: enhancement
#58 - Could not load assembly error
Issue -
State: closed - Opened by maganuk over 6 years ago
- 2 comments
#57 - Metadata
Pull Request -
State: closed - Opened by mrahhal over 6 years ago
#56 - Create a resx file to store the migration's metadata
Issue -
State: closed - Opened by mrahhal over 6 years ago
#55 - Version for package `Migrator.EF6.Tools` could not be resolved
Issue -
State: closed - Opened by marchy over 6 years ago
- 10 comments
#54 - Add a "runtime" option
Pull Request -
State: closed - Opened by mrahhal almost 7 years ago
#53 - Unhandled Exception: System.ComponentModel.Win32Exception: The system cannot fin d the file specified
Issue -
State: closed - Opened by buraktamturk almost 7 years ago
- 9 comments
#52 - Update DotnetToolDispatcher to fix problem with latest sdk
Pull Request -
State: closed - Opened by mrahhal almost 7 years ago
#51 - Problem with newest .net core sdk (2.1.2)
Issue -
State: closed - Opened by mrahhal almost 7 years ago
- 3 comments
#50 - Microsoft.DotNet.Cli.Utils cannot install in asp.net core 2 project with Migrator.EF6
Issue -
State: closed - Opened by joeizang almost 7 years ago
- 4 comments
#49 - Binding redirects lost because of manual relaunching of tool
Issue -
State: open - Opened by nphmuller almost 7 years ago
- 2 comments
#48 - Rename Param ConnectionString to ConnectionStringForMigration
Issue -
State: closed - Opened by xrkolovos almost 7 years ago
- 5 comments
#47 - Ensure the tool works with the new .net 2.0 sdk
Issue -
State: closed - Opened by mrahhal about 7 years ago
- 3 comments
#46 - Support for net47 and later
Pull Request -
State: closed - Opened by Abdruggi about 7 years ago
- 3 comments
#45 - Not working with projects targeting net47
Issue -
State: closed - Opened by Abdruggi about 7 years ago
- 10 comments
#44 - Add `migrations remove` command
Issue -
State: open - Opened by mrahhal over 7 years ago
Labels: enhancement
#43 - Newtonsoft.Json v10 problem
Issue -
State: closed - Opened by hikalkan over 7 years ago
- 14 comments
#42 - Migrations being generated for a context that I don't want
Issue -
State: closed - Opened by armille3 over 7 years ago
- 13 comments
Labels: bug
#41 - Crash after calling dotnet ef enable
Issue -
State: closed - Opened by armille3 over 7 years ago
- 5 comments
#40 - Version 1.1.1 will cause the CMD window crash
Issue -
State: closed - Opened by viewtance over 7 years ago
- 6 comments
#39 - BadImageFormatException was unhandled -- An attempt was made to load a program with an incorrect format.
Issue -
State: closed - Opened by wh1sp3r over 7 years ago
- 1 comment
#38 - "Sequence contains no matching element" error when -c options specifies missing/mis-typed context
Issue -
State: closed - Opened by marchy over 7 years ago
- 4 comments
Labels: enhancement
#37 - Error when migrations are inside the webapp project
Issue -
State: closed - Opened by wh1sp3r over 7 years ago
- 18 comments
Labels: wontfix
#36 - VS 2017 format
Issue -
State: closed - Opened by hikalkan over 7 years ago
- 6 comments
#35 - Migrate to dotnet tooling 1.0
Pull Request -
State: closed - Opened by mrahhal over 7 years ago
- 7 comments
#34 - Support for csproj
Pull Request -
State: closed - Opened by Abdruggi over 7 years ago
- 1 comment
#33 - The argument 'nameOrConnectionString' cannot be null, empty or contain only white space.
Issue -
State: closed - Opened by jimbo74 over 7 years ago
- 12 comments
#32 - Unhandled Exception: Microsoft.DotNet.Cli.Utils.CommandUnknownException: No executable found matching command "dotnet-ef"
Issue -
State: closed - Opened by joeizang almost 8 years ago
- 6 comments
#31 - Asp Net Core 1.1 Support
Issue -
State: closed - Opened by iyhammad almost 8 years ago
- 5 comments
#30 - Error Generating Migrations
Issue -
State: closed - Opened by DOTang almost 8 years ago
- 4 comments
#29 - Can't update database after scaffolding migrations
Issue -
State: closed - Opened by DOTang almost 8 years ago
- 5 comments
#28 - Any chance to extend functionality to be able to supply a connection string and provider and/or startup project?
Issue -
State: closed - Opened by DOTang almost 8 years ago
- 7 comments
#27 - Support for Multiple Db Context per project
Issue -
State: closed - Opened by iyhammad about 8 years ago
- 5 comments
#26 - Fixed issue where MigrationsDirectory property in DbMigrationConfiguration was ignored.
Pull Request -
State: closed - Opened by nphmuller about 8 years ago
- 1 comment
#25 - Don't locate DbContexts and DbMigrationsConfigurations that cannot be constructed
Pull Request -
State: closed - Opened by nphmuller about 8 years ago
- 5 comments
#24 - Specifying a target Migrations directory.
Issue -
State: closed - Opened by AlonCG about 8 years ago
- 10 comments
#23 - Unhandled Exception: System.ComponentModel.Win32Exception( 32 bit windows )
Issue -
State: closed - Opened by redpanda321 about 8 years ago
- 4 comments
#22 - Value cannot be null. Parameter name: type
Issue -
State: closed - Opened by marchy about 8 years ago
- 2 comments
#21 - An unhandled exception of type 'System.Reflection.TargetInvocationException' occurred in mscorlib.dll
Issue -
State: closed - Opened by jmbalanag about 8 years ago
- 2 comments
#20 - Support for SQLite / SQL CE
Issue -
State: closed - Opened by jmbalanag about 8 years ago
- 2 comments
#19 - running "dotnet ef migrations enable" fails to find matching command "dotnet-ef"
Issue -
State: closed - Opened by Eisenstein about 8 years ago
- 2 comments
#18 - Possibility to have the dbcontext in a separate project
Issue -
State: closed - Opened by mhobl about 8 years ago
- 2 comments
#17 - Unhandled Exception: Microsoft.DotNet.Cli.Utils.CommandUnknownException
Issue -
State: closed - Opened by michaelmcneilnet about 8 years ago
- 1 comment
#16 - ASP.NET Core 1.0 Support?
Issue -
State: closed - Opened by RehanSaeed over 8 years ago
- 1 comment
#15 - Update project.json
Pull Request -
State: closed - Opened by RehanSaeed over 8 years ago
- 3 comments
#14 - Finish incomplete migration of the WithIdentity sample to ASP.NET Core RC2
Pull Request -
State: closed - Opened by rstarkov over 8 years ago
- 1 comment
#13 - A couple more commands
Issue -
State: closed - Opened by sagoo33 over 8 years ago
- 3 comments
#12 - Consider initializing the target project so that the context can be created from DI
Issue -
State: closed - Opened by mrahhal over 8 years ago
- 1 comment
Labels: enhancement
#11 - Tool not building the target project before dispatching commands
Issue -
State: closed - Opened by mrahhal over 8 years ago
- 1 comment
Labels: bug
#10 - Getting error message in command line when running dotnet ef enable
Issue -
State: closed - Opened by Ksyruz over 8 years ago
- 5 comments
#9 - Command Exception: No executable name found matching command "dotnet-ef"
Issue -
State: closed - Opened by ilmax over 8 years ago
- 22 comments
#8 - Add features to closely align with the EF Core tools counterpart
Issue -
State: closed - Opened by mrahhal over 8 years ago
- 1 comment
Labels: enhancement
#7 - Porting to RC2
Pull Request -
State: closed - Opened by mrahhal over 8 years ago
#6 - Porting to RC2
Issue -
State: closed - Opened by tuespetre over 8 years ago
- 9 comments
#5 - Can't get migrations to work
Issue -
State: closed - Opened by findulov over 8 years ago
- 4 comments
#4 - 'ApplicationDbContext' does not contain a definition for 'Add'
Issue -
State: closed - Opened by joshiji over 8 years ago
- 3 comments
#3 - You Don't need to Hard Code the Connection String
Issue -
State: closed - Opened by RehanSaeed over 8 years ago
- 2 comments
Labels: discussion
#2 - Dependency Microsoft.Extensions.CommandLineUtils.Sources cannot be resolved !
Issue -
State: closed - Opened by gfrSE over 8 years ago
- 3 comments
#1 - Add a note about the CommandLineUtils dependency
Issue -
State: closed - Opened by tuespetre over 8 years ago
- 4 comments