Known Issues

I encourage you to mess around with a clone of this project, it uses itself in a few different ways so it is a good example of itself. Try renaming a few things, adding new projects etc and see what happens. I promise you nobody will die.

Current Issues

Check the current Issue tracker queue, I'm not going to duplicate that here.

Renaming the Source project.

Yup, that will definitely break it. CodeLinkerLog.txt will let you know. You will need to fix that yourself.

• Manually edit the destination .xxproj file(s) and change the <source: or
• Grab your favourite grep tool and replace <source: xxx.xxproj with the new name but
• I wouldn't re-recycle the original source over the top of the destination(s) you need to update because you will overwrite things that were changed and added later. It will reset that destination project to the default, an exact replica of the source but with links instead of its own files. You could sort that out with a diff tool but is it really easier than find-replace one tiny bit of text?

Project References

When you create a new project using the GUI it keeps all the old references from the source project. You will need to change them if you are changing the platform, 3rd party libraries etc.

If / when you add or change a reference in the original source project then it may have knock-on effects in any project that links back to it - you may have to update the references in those projects too. Fully qualified namespaces in some key places in your code may save you a few late night mysteries.

Nothing about Project references is managed by Code Linker, that it outside the scope of this app.

Nuget packages

This is the same case as for References but is possibly more complicated (or not, as of writing I haven't had much Nuget action in this context yet). Having said that, any packages you add / remove / update should be managed properly by Nuget and they should get the correct versions. That's what Nuget does, right?

Refactoring / Renaming things, especially file names

Refactoring may get tricky at times. I found that often I had to rebuild the solution so Visual Studio & Resharper could catch up to what is going on before it would let me do some name-change refactors. If you rename a file in the source project then you will notice all the destination projects break because they have a link that is suddenly invalid. Rebuild the source and run CodeLinker on it again to refresh the links.

Copying a Destination Project

• probably Will work if you copy it to a folder that has the same relationship to the original source ie. you don't need to edit the <Source: in the Link Zone Placeholder to get it to update itself. Keeping to the same folder depth is essential to this. You may be better off re-recycling from the original source and merging any references, Nuget packages etc with a diff tool.
• probably Won't work if you need to edit the <Source: in the Link Zone Placeholder to get it to link. The process of creating a new destination project also checks for existing links, wildcards etc. so you're probably going to break something.