Hi there,
Can anyone explain why the assembly qualified names seen in the ".resx" file
for each form in an application aren't kept up-to-date by Visual Studio. For
instance, if a dialog uses a user control from some other library in the
same solution, the user control's assembly qualified name will appear in the
dialog's ".resx" file. Each time the control's library is compiled however,
the library's version is incremented but the ".resx" file continues to show
the original version number. How then does Visual Studio load it when the
dialog is displayed in the Visual Studio designer? If all projects are
signed then the control's library identity won't match what's in the '.resx"
file but Visual Studio seems to ignore this. Can anyone shed any light on
the situation? Thanks in advance.
Can anyone explain why the assembly qualified names seen in the ".resx" file
for each form in an application aren't kept up-to-date by Visual Studio. For
instance, if a dialog uses a user control from some other library in the
same solution, the user control's assembly qualified name will appear in the
dialog's ".resx" file. Each time the control's library is compiled however,
the library's version is incremented but the ".resx" file continues to show
the original version number. How then does Visual Studio load it when the
dialog is displayed in the Visual Studio designer? If all projects are
signed then the control's library identity won't match what's in the '.resx"
file but Visual Studio seems to ignore this. Can anyone shed any light on
the situation? Thanks in advance.