http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=117453
When the projects in Visual Studion 2005 are compiled, different satellite assemblies are normally generated in different folders e.g. \obj\release\<%lang%>\ where <%lang%> can be fr, gb and pt, just to mention a few.
The INF file contents will also point to the different resource aseemblies for each resource. (though the name of these assemblies are same, the path are still different). However, I think the CabWiz.exe believes that all these assemblies are same (as they share the same name), and hence include the same assembly in the cab file for each different language.
The issue and workarounds described in the above link.
When the projects in Visual Studion 2005 are compiled, different satellite assemblies are normally generated in different folders e.g. \obj\release\<%lang%>\ where <%lang%> can be fr, gb and pt, just to mention a few.
The INF file contents will also point to the different resource aseemblies for each resource. (though the name of these assemblies are same, the path are still different). However, I think the CabWiz.exe believes that all these assemblies are same (as they share the same name), and hence include the same assembly in the cab file for each different language.
The issue and workarounds described in the above link.
_512.jpg)
1 comments:
Nice post you got here. It would be great to read more concerning that theme. The only thing it would also be great to see on this blog is some photos of some devices.
Kate Watcerson
Cell phone jammer
Post a Comment