By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,969 Members | 2,250 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,969 IT Pros & Developers. It's quick & easy.

Resgen.exe error: Invalid ResX input, SerializationException

P: n/a
When manually running resgen.exe from the command prompt (Visual Studio .NET
2003 command prompt) I get the following error:

[resgen] error: Invalid ResX input.
[resgen] error: Specific exception: SerializationException Message: Invalid
ResX input. ---> SerializationException: Cannot find the assembly Common,
Version=1.0.1905.1173, Culture=neutral, PublicKeyToken=null.
[resgen] 2 error(s).

The file within the project it is erroring on is a custom control.

I have seen this error in the newsgroups, but no posts on a proper solution.

If I build the solution in the Visual Studio .Net 2003 IDE, it builds fine.
However We are trying to build a solution from the command line using Nant.
When Nant runs the build, it first runs resgen and then gets the same error
that occurs when running resgen.exe manually from the command line.

Any help would be appreciated.

Frank Jones

Jul 21 '05 #1
Share this Question
Share on Google+
1 Reply

P: n/a
Hi Frank,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that when you use resgen.exe from the
command line, an exception is thrown. But this does not occur in the IDE.
If there is any misunderstanding, please feel free to let me know.

As far as I know, until .NET 2.0 this tool did not support compiling
resources with references to assemblies that are not stored in the GAC. In
Nant, you copy the assemblies needed to a temp directory and launch resgen
there, or try to use a fileset support in ResGenTask.

Please check the following thread for more information:******.../msg03136.html

Kevin Yu
"This posting is provided "AS IS" with no warranties, and confers no

Jul 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.