Unable To Load Resource File 1003 Claw
Join GitHub today
Captain Claw Error Unable Load Resource File 1003 and other critical errors can occur when your Windows operating system becomes corrupted. Count me in this category as well. Have tried checking the paths, all is good, even added a few more as well. Out of interest, are you guys running XP?
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upComments
commented Oct 10, 2014
Try loading the resource, this will fail. If you ignore the namespace and change the above to not include the namespace it works fine. This is a very common pattern and it worked in the old world so although there is a workaround it is super painful to keep changing this when you are porting your application to vNext and have large number of resource files (which some projects do). |
commented Oct 15, 2014
We need a few pieces to fall into place before we can solve this properly. Such as pre-processors. |
added a commit to autofac/Autofac that referenced this issue Nov 28, 2014
Added yucky #if ASPNETCORE50 directives in resource designer files to…
commented Jan 22, 2015
@muratg@Eilon I wanna change our resource format for beta3 |
commented Jan 22, 2015
This also breaks trying to use EF6 migrations, as the embedded filenames for generated .resx files don't match what EF is looking for. |
modified the milestones: 1.0.0-beta3, BacklogJan 22, 2015
Unable To Load Resource Jnlp
added the 1 - Ready label Jan 22, 2015
added a commit to autofac/Autofac that referenced this issue Feb 8, 2015
Fixed unit tests failing because ofaspnet/dnx#738
commented Feb 10, 2015
@davidfowl rc1? |