Visual Studio has a Create GUID tool (Tools > Create GUID).
What is it for? Can you remember what was the last time you used it?
I just can't imagine why i should copy into the clipboard a new GUID with that tool.
Visual Studio has a Create GUID tool (Tools > Create GUID).
What is it for? Can you remember what was the last time you used it?
I just can't imagine why i should copy into the clipboard a new GUID with that tool.
I've used it many times to get a GUID without having to write and run some code or open SQL Management Studio.
It's a very useful tool for those who develop and maintain COM components. Need to introduce a new registry-exposed class or interface? You need a new GUID. With this tool you click "New GUID", select "Registry format", copy it to the clipborad and then paste into a IDL file.
WiX (installer toolkit) projects require a lot of GUIDs. I use it often and often.
GUIDs are very useful when you wish to create a unique identifier to a resource.
In C# you can use :
System.Guid.NewGuid();
[Guid("8B92766B-825F-409d-BC32-B3723D617A93"), ClassInterface(ClassInterfaceType.None), ProgId("Apollo.WS"), ComVisible(true)]
public sealed class WS : ServicedComponent, IWSFSAPLProxy {}
Here you have. That GUID came from the Create GUID tool
why do our systems need to be full of this cryptic cr4p. If it it a useful name after the last } at least we know we are not corrupting something important. Why is this mechanism used???