building from source

[Moorea]

looks like you forgot to make or check in the changes to

mojo_app.rc(765): error RC2135: file not found: E:\d\sou\cpp\mojo_svn\mojo_art\wow-logo-70x69.bmp


replace:
IDB_WOW_LOGO BITMAP "E:\\d\\sou\\cpp\\mojo_svn\\mojo_art\\wow-logo-70x69.bmp"
IDB_WOW_LOGO_GREEN BITMAP "E:\\d\\sou\\cpp\\mojo_svn\\mojo_art\\wow-logo-green-70x69.bmp"
by
IDB_WOW_LOGO BITMAP "..\\mojo_art\\wow-logo-70x69.bmp"
IDB_WOW_LOGO_GREEN BITMAP "..\\mojo_art\\wow-logo-green-70x69.bmp"



For
1>C:\Windows\Microsoft.NET\Framework\v4.0.21006\Mi crosoft.Common.targets(1886,9): error MSB3323: Unable to find manifest signing certificate in the certificate store.
any idea what I need to do (install some clickonce sdk; or something ?)

[Freddie]

looks like you forgot to make or check in the changes to

mojo_app.rc(765): error RC2135: file not found: E:\d\sou\cpp\mojo_svn\mojo_art\wow-logo-70x69.bmp


replace:
IDB_WOW_LOGO BITMAP "E:\\d\\sou\\cpp\\mojo_svn\\mojo_art\\wow-logo-70x69.bmp"
IDB_WOW_LOGO_GREEN BITMAP "E:\\d\\sou\\cpp\\mojo_svn\\mojo_art\\wow-logo-green-70x69.bmp"
by
IDB_WOW_LOGO BITMAP "..\\mojo_art\\wow-logo-70x69.bmp"
IDB_WOW_LOGO_GREEN BITMAP "..\\mojo_art\\wow-logo-green-70x69.bmp"



For
1>C:\Windows\Microsoft.NET\Framework\v4.0.21006\Mi crosoft.Common.targets(1886,9): error MSB3323: Unable to find manifest signing certificate in the certificate store.
any idea what I need to do (install some clickonce sdk; or something ?)

Was that a change I made or was it a change you made when you edited the RC file by hand?

If it was my change, I think I was just trying to change an absolute path to a relative one.

The files are in the repository dated Jan. 6. I just looked on Google.

I don't know what's wrong. Do you have any ideas?

[Moorea]

the line above that one was something I stepped on a while ago, from very early compile error; the 2 next ones mentioned now is what I've been saying since post #21 and when you said in post #23 "I'll add then" maybe I should have picked up - it's not about adding but just removing the bogus absolute path

so yes you need to edit by hand mojo_app.rc at line 765 and replace:
IDB_WOW_LOGO BITMAP "E:\\d\\sou\\cpp\\mojo_svn\\mojo_art\\wow-logo-70x69.bmp"
IDB_WOW_LOGO_GREEN BITMAP "E:\\d\\sou\\cpp\\mojo_svn\\mojo_art\\wow-logo-green-70x69.bmp"
by
IDB_WOW_LOGO BITMAP "..\\mojo_art\\wow-logo-70x69.bmp"
IDB_WOW_LOGO_GREEN BITMAP "..\\mojo_art\\wow-logo-green-70x69.bmp"
so it works for me and everybody who would checkout from source (it'll still work for you too)
if the UI automatically generates/edit that when you add a resources you should add a todo postit note for you to manually fix them each time you add a new one; or maybe write a simple sed like script to replace "E:\\d\\sou\\cpp\\mojo_svn\\" by ".." before check in


ps1: did you get the dump I emailed ?
ps2: any idea about clickonce/installer?

[Freddie]

Oh you were telling me to replace. I thought you were showing me an error message from something.

I thought it looked kinda strange for an error message.

[Moorea]

thx, the resource file is fixed in 21 - any idea about the installer error message ?

[Freddie]

I know generally what it's about but I don't know how to fix it. If you want to read about Windows certificate store and tell me, I'll do it.

The clickonce installer is looking for my public key to add it to the installation package. That key isn't part of the source code. It's something (I think) that Windows keeps in kernel mode data structures on the PC where I build Mojo. There must be some way to export it to other PCs but I don't know how.

It might be easier to use your own certificate. Visual Studio will make one for you when it builds the installer if you select an option or press a button in "Properties" in the MojoInstaller project. I forget how to do it exactly but it's very easy. Only thing is, though, if you do that and you distribute Mojo to yourself you may screw up your Mojo installation since ClickOnce may think the key is wrong.

[Moorea]

Ah found ! In "Signing" tab, just uncheck "Sign the clickonce manifest" and presto, it works without errors now

If you created a test certificate, there is 0 security to that so you may as well uncheck it (until you get a real cert)

[Freddie]

Ah found ! In "Signing" tab, just uncheck "Sign the clickonce manifest" and presto, it works without errors now

Good.

If you created a test certificate, there is 0 security to that so you may as well uncheck it (until you get a real cert)

If I uncheck it, ClickOnce won't publish it. It requires a signature for publication.

[Moorea]

hmm odd I was able to publish to my local directory - is there something special running on the web side ?

[Freddie]

hmm odd I was able to publish to my local directory - is there something special running on the web side ?

I was just relying on ClickOnce's documentation. They say the certificate has to be signed in order to publish it.