Roachy

Q1.

I've been creating test certificates for my app without really understanding much about them, only that I must have one otherwise I can't publish.

I've noticed that they are only valid for 12 months

If I am giving/selling an app. to others what happens after the certificate expires

Is there a way of not including a certificate

Q2.

I have 2 separate projects but they have identical GUID's.

I think this is due to me using a lot of code from project 1 and using it in project 2.

I have installed both projects on a test machine and both work fine. However when going to Uninstall them from Add/Remove Programs I notice that project 2 doesn't show the file size.

I'm assuming identical GUID's is not a good idea but is it possible/safe to change it manually



Re: Visual Basic Express Edition 2 Q's: Test Cetificate expiry date and Assembly Information: GUID

ReneeC

Roachy, these are interesting questions.

You do not have to have a certificate to give software away or to sell it. I give a lot of software away and I've never had a certificate.

It's the second question that I find technically interesting. By definition, a guid is supposed to be unique to time and place. That's what it's for. There have only been one or two cases where there have ever been identical guid's. It does not come from shared code. Supposedly a new Guide is generated every time you compile. I don't know what your project structure looks like but the identical guids have to come from the way you are building your project.






Re: Visual Basic Express Edition 2 Q's: Test Cetificate expiry date and Assembly Information: GUID

Roachy

ReneeC,

Thanks for your reply.

I've just tested it and if I leave the 'Sign the Click Once Manifests' unchecked and then publish, a test certificate is automatically generated and the 'Sign the Click Once Manifests' is automatically checked.

If you know of any way of getting around this then please let us know.

I don't think I'm doing anything strange when I do my builds (but then again I'm no expert).

Is there a right/wrong way

Do you think it's safe to change the GUID manually





Re: Visual Basic Express Edition 2 Q's: Test Cetificate expiry date and Assembly Information: GUID

ReneeC

I've never used a certificate and my code is in a lot of places so I assume certificate expiration is not an issue.

As far as the Guids, whatever is occuring is occuring in the way you have your project(s) structure, of which I know nothing. So you need to say a lot more about that.

There is more than one executable assembly And they both have the same guid






Re: Visual Basic Express Edition 2 Q's: Test Cetificate expiry date and Assembly Information: GUID

Tall Dude

On Q2, I don't know much about GUIDs but I

dug up some code which seems to make a useable GUID.

Public Class Form1

Private Sub Button1_Click(ByVal sender As System.Object, _

ByVal e As System.EventArgs) Handles Button1.Click

TextBox1.Text = getGUID()

End Sub

Private Function getGUID() As String

GetGUID = "{" & _

System.Guid.NewGUID().ToString & "}"

End Function

End Class






Re: Visual Basic Express Edition 2 Q's: Test Cetificate expiry date and Assembly Information: GUID

ReneeC

That's rather easy to do, tall dude. There's a bug in the debugger believe it or not and it shows all guids as being empty

so you'll see a frequent testline in my code;

Dim a As String = Guid.NewGuid.ToString

because that's the only way you can ever see a guid.






Re: Visual Basic Express Edition 2 Q's: Test Cetificate expiry date and Assembly Information: GUID

Tall Dude

In the VB express edition, you can:

'Project', 'Project Name Properties',

Application tab, 'Assembly Information' button

and see the GUID in the IDE.






Re: Visual Basic Express Edition 2 Q's: Test Cetificate expiry date and Assembly Information: GUID

ReneeC

I'm quite aware of that. And it doesn't have brackets.

But I believe to do that you are fixing a symptom. At the same time as I said earlier not enough is known about the project's structure to make any meaningful comment at all.






Re: Visual Basic Express Edition 2 Q's: Test Cetificate expiry date and Assembly Information: GUID

Roachy

I came across this in the Help "To publish an application using ClickOnce deployment, you must sign the application and deployment manifests for the application with a public/private key pair."

I still don't understand how you are doing your publishing without a certificate, can you explain what you are doing

I'm not sure what you want to know about the structure





Re: Visual Basic Express Edition 2 Q's: Test Cetificate expiry date and Assembly Information: GUID

ReneeC

Whoops .....

I'm using vs2005 Team Suite and it has custom build projects. I'm sorry I virtually never use click-once publication.