Changes in resolving .resx in Visual Studio 2010?

Answer 1

I know this isn't exactly an answer but I thought of some things that might help you if you have really hit a brick wall on this ...

It might be useful to be able to look at the .net code and see what is happening. If you want to try this, do the following:

• In Visual Studio go to Tools -> Options -> Debugging -> Symbols

• Where it says Symbol file (.pdb) locations, type

  http://msdl.microsoft.com/download/symbols

• Supply a path where it says "Cache symbols from symbol store to this directory:"

• Hit ok
• A dialog will appear, accept the terms

Now when you debug you should be able to step into the resource manager code.

If this still doesn't work for you and all else fails you can always work around your problem by writing your own resource manager. You can do this by implementing IResourceReader. I found a sample here that gives an example:

Custom Resource Reader

Answer 2

It should just work. So the question is to figure out what is missing:

Are the right DLLs in the right sub folders in your bin dir?

If you dump the loaded DLLs (AppDomain.CurrentDomain.GetAssemblies()) before and after these calls, is it showing you that it has loaded the DLLs?

Does IIS have proper permission to the DLLs?

Does it work if you compile in .NET 3.5 mode in VS2010, if not what is the difference in the compiled DLLs?

Answer 3

Hi Guys,

I actually didnt figure out what was going wrong. But since VS2010 and .NET 4.0 was released yesterday, I got the chance to try it out with the released Versions and it worked fine.

So I guess it was just a bug in the RC which was fixed now.

Thx for the Help!