J
John Cullen
I have uncovered an interesting problem with resource only DLLs. If I
create a project with a long name and the name includes periods ("."), the
IDE will fail to kick off the linker. The resource compiler seems to
successfully compile the .rc to a .res, but the linker never fires up. If I
force a link, the DLL will be created but will contain no resources.
An example project name that fails to link is
"My.Long.Named.Resource.Only.Project". If I rename the project to
"MyLongNamedResourceOnlyProject" or "My.Test", I get the resource only DLL
as expected.
Is this a bug in VS.net 2003?
create a project with a long name and the name includes periods ("."), the
IDE will fail to kick off the linker. The resource compiler seems to
successfully compile the .rc to a .res, but the linker never fires up. If I
force a link, the DLL will be created but will contain no resources.
An example project name that fails to link is
"My.Long.Named.Resource.Only.Project". If I rename the project to
"MyLongNamedResourceOnlyProject" or "My.Test", I get the resource only DLL
as expected.
Is this a bug in VS.net 2003?