Last post Jun 12, 2007 06:02 PM by mp_mdavies
Jun 08, 2007 04:55 AM|mp_mdavies|LINK
I'm currently trying to make a language satellite assembly work for a web deployment project but am unable to get the resulting dll's to work in the app.
The reason is we want to be able to update the language dll's without doing a new release and instead just compile the right files.
The first difference I can spot is that the old dll was named 'MP_Sprint.resources.dll' and the new dll is named 'Sprint3_deploy.resources.dll'. If someone can tell me how to compile for a WDP I would be really grateful.
Here are the command's I'm running:
ProcessStartInfo newPsi = new ProcessStartInfo(Server.MapPath("..\\LocalizationKit\\Utilities\\ResGen.exe"), "..\\" + ddlLanguageFiles.SelectedValue + " ..\\resources.strings." + ddlLanguageFiles.SelectedItem.Text + ".resources");
newPsi = new ProcessStartInfo(Server.MapPath("..\\LocalizationKit\\Utilities\\AL.exe"), "/nologo /t:lib /culture:..\\" + ddlLanguageFiles.SelectedItem.Text + " /embed:..\\..\\" + ddlLanguageFiles.SelectedItem.Text + "\\resources.strings." + ddlLanguageFiles.SelectedItem.Text
+ ".resources /out:..\\Bin\\" + ddlLanguageFiles.SelectedItem.Text + "\\" + "Sprint3_deploy.resources.dll");
Jun 12, 2007 06:02 PM|mp_mdavies|LINK
Ok People I think I might have a clue as to what's happening.
When the site compiles in the WDP it is picking up the sgKey.snk in the root of the directory. Now I think the WDP is finding this and signing my bin files. Now I've tried to sign my new files with the key by adding the /KeyFile to AL.exe but it still
doesn't work. Does anyone have any sugestions as to how to sign a file to make it work with an existing application?