Problem
The GUID for an assembly should, in theory, be a unique way to identify the .dll. However, all cookiecutter projects will have the same GUID. There are, as it happens, a few people who look for specific GUIDs when doing magicTM.
In addition, the project GUIDs should apparently be unique (which would prevent problems when moving projects from solution to solution? Most of us would never notice)
Maybe Do This
There's a command-line option to generate mostly-unique GUIDs in Linux, and there are web options, but I don't know about Windows, and I don't even know if cookiecutter can run commands. Maybe there is a library already in json? I haven't looked any further into this yet.
At a worst-case scenario, the user could be given a website suggestion and prompted to enter GUIDs?
But perhaps more research is required.
Problem
The GUID for an assembly should, in theory, be a unique way to identify the .dll. However, all cookiecutter projects will have the same GUID. There are, as it happens, a few people who look for specific GUIDs when doing magicTM.
In addition, the project GUIDs should apparently be unique (which would prevent problems when moving projects from solution to solution? Most of us would never notice)
Maybe Do This
There's a command-line option to generate mostly-unique GUIDs in Linux, and there are web options, but I don't know about Windows, and I don't even know if cookiecutter can run commands. Maybe there is a library already in json? I haven't looked any further into this yet.
At a worst-case scenario, the user could be given a website suggestion and prompted to enter GUIDs?
But perhaps more research is required.