danielsaidi/cloney

Cloney is an open-source client application that lets you clone .NET solutions

cloney's Issues

Auto-create target folder

Whenever a user enters a non-existing target folder, Cloney should be able to auto-create it.

STABILIZE these factors

The Encoding resolver does not work for certain file types, e.g. .exe. This class should be removed and encoding handled in another way.

In Windows 8, the selected target path is not applied. The cloned files end up in C:

Fix these issues, setup a backlog for encoding and release a new version together with an updated site asap!

Target path suddenly stopped working

Look into this...is it because of the marged pull requests?

Launch Cloney from other folder

Ensure that Cloney can be started from another folder than the application folder.

Try:

• cloney
• cloney --modal
• cloney --help

Incorrect target folder

In Cloney 0.99.0, the target folder ends up in the same folder as the source folder.

Expose target path in wizard

Just like for the command line application, the wizard should also display where a cloned file/folder ends up.

UTF-8 Byte-Order-Mark problem

It looks like when I clone a file, Cloney either adds or removes the BOM. At least it changes it and my git commit is polluted :)

Text encoding

Encoding continues to confuse Cloney. Neither the first (Klerks) implementation, nor the streamreader one does the job. Add a @ in an AssemblyInfo file and watch it break.

Problem cloning

Try this example:
http://code.msdn.microsoft.com/ASPNET-Web-API-JavaScript-d0d64dd7
It uses Comments as the project name, comments as a javascript variable,
comment as another variable and embedded "comments" in comments
naturally :-(
More standardization from MS?
Cloney was a great start but I had to beat it into submission manually!

BTW, I love Cloney !!!

Maybe skip "packages"-folder?

Since lot's of nuget-files are included in a solutions package-folder maybe Cloney should skip the packages folder when performing the clone?

Says it's ready when in fact something went wrong

I just tried to clone a project when the project was open in Visual Studio (guess that's not a good idea but anyway).

The clone started and just some files where transferred before this message was shown:

In fact the job stopped at the "storage.ide"-file since it was locked by Visual Studio. I guess that we might be able to come up with a better error message?

Better ignore/plain copy handling

Find a way to extend the ignore and plain copy lists when cloning a solution.

Opt.1) More input parameters, e.g. --ignore="*.foo,my-image.jpg"
Opt.2) A .gitignore-like approach

Better warning if no sln file exists in source folder

Context menu does not work in Windows 8

The Cloney context menu does not appear in Windows 8. Either add a second registry key pair for Windows 8 (http://www.c-sharpcorner.com/UploadFile/7e39ca/edit-right-click-context-menu-in-windows-8/) or provide an installation option for specifying whether or not to install context menu for Windows 8.

A trailing backslash makes a difference

When cloning from Bla\' toBlaBla, the new files created will be calledBlaBlaBla.csproj` - missing the separating backslash.

Encoding

When cloning stuff with Cloney, special characters (like Swedish, copyright marks etc) will be messed up.

New line in sln-file

Hi,

Cloney is a really nice tool! Thx!

There are some small bugs. I am too laze to report it at github because I have no account.

1. If I have many large files in a project, Cloney stops copying before copying all files. I cannot reproduce this problem and it does not appear always.
2. There is another reproducable bug: the copied sln file starts with an empty line. Vs 2010 does not start with it but everything seems to work fine.

Small enhancement: adding an ignore filter to prevent copying every file/folder. E.g. svn folder, sdf files, x64 folder, debug folder etc. should not be copied. I generate several image files in the project folder which also should not be copied. Maybe you can add a file where everybody can make his/her personal ignore list.

Greetings
Brater

Remove write lock on copied files

Ability to Clone a project within a solution

I have project "templates" that I'd like to copy with ability to modify namespace.

Expose target path in command line application

Today, Cloney only displays the source path when cloning. If the target path should be strange, or if Cloney resolves it incorrectly, the user has no possibility to know that.

When cloning a folder or file, Cloney should therefore display:
source
=> target

Packages-folders processed

Just cloned a project an noticed the following:

• node_modules-folder that is placed in a in subfolder/sub-project gets processed
• packages folder get's processed.

Is this by design or should we make sure to exclude them?

Fixing project GUIDs

Would be great, if Cloney fixed the Guids for the projects, solutions and in AssemblyInfo (Com Visibility)