Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

non latin characters in migration name #8483

Closed
dvdobrovolskiy opened this issue May 16, 2017 · 2 comments
Closed

non latin characters in migration name #8483

dvdobrovolskiy opened this issue May 16, 2017 · 2 comments
Assignees
@bricelam
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Milestone
2.0.0

Comments

@dvdobrovolskiy
Copy link

Accidentally named migration with non latin characters like

PM> add-migration ControlledObjects_щквук
To undo this action, use Remove-Migration.
add-migration : Value does not fall within the expected range.
At line:1 char:1
+ add-migration ControlledObjects_щквук
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (:) [Add-Migration], ArgumentException
    + FullyQualifiedErrorId : System.ArgumentException,Add-Migration

Now I am stuck, cant Remove-Migration because of build error

Severity	Code	Description	Project	File	Line	Suppression State
Error	CS2001	Source file 'C:\Users\dima\documents\visual studio 2017\Projects\TNPK\TNPK\Data\Migrations\20170516112547_ControlledObjects_骢�.cs' could not be found.	TNPK	C:\Users\dima\documents\visual studio 2017\Projects\TNPK\TNPK\CSC	1	Active
@bricelam
Copy link
Contributor

What version are you using? This looks like #6722 which was fixed in the 1.0.0-msbuild3 pre-release of tools.

@dvdobrovolskiy
Copy link
Author

1.1.2
It seems like different. File name of migration was generated with trash instead of non latin characters. Renaming file solved this issue

@ajcvickers ajcvickers added this to the 2.0.0 milestone May 17, 2017
@bricelam bricelam modified the milestones: 2.0.0-preview2, 2.0.0 May 30, 2017
@bricelam bricelam added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label May 30, 2017
@bricelam bricelam mentioned this issue May 30, 2017
Merged
@ajcvickers ajcvickers modified the milestones: 2.0.0-preview2, 2.0.0 Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bricelam bricelam

Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Projects
None yet
Milestone
2.0.0
Development

No branches or pull requests
3 participants
@bricelam @ajcvickers @dvdobrovolskiy