dnikolovv / solution-snapshotter Goto Github PK

Pick a few sample projects (both csharp and fsharp) and write automated tests against them.

Are you sure that overview.md must be mandatory?

Actual:

When uploading the generated VSIX to the VS Marketplace, you must put it under the Tools category.

Expected:

You should be able to upload the VSIX under Templates.

It seems that the category is inferred by Visual Studio and cannot be changed. Research how and why this is happening and refactor the application to generate a valid VSIX that can be uploaded as a template.

Not that this will bring any significant value, but it bugs the hell out of me :)

The vsixmanifest generation is kind of fragile.

It relies on having a "template" vsixmanifest file with some empty XML tags inside the Metadata. When you want to add additional Metadata tags, you also have to edit the WizardTemplate.zip, which shouldn't really be necessary.

Hello!
Thank you for creating this project and making it available as Free and MIT license. This was really helpful for me to create templates for microservices.

While using it, I found multiple issues:

1. --file-extensions-to-ignore option isn't quite working. I tried it with value ".csproj.user" option but it seemed files were still being copied. It didn't work with commandline arguments or from-file with config file option.

2. when using solution-snapshotter.exe from-file input.config if the input.config has below as the value for folders to ignore, then it doesn't really ignore them. I tried the below possible variations and non of them worked.
   <add key="folders to ignore" value="bin, packages, obj, lib, .git, .vs, node_modules, TestResults" />
   another way
   <add key="folders to ignore" value="bin packages obj lib .git .vs node_modules TestResults" />
   May be there is another way to use it. Can you please clarify if am I doing something wrong?

3. For some reason all the files that get copied, I noticed the UTF-8 bom gets removed hence the stylecop warning comes up. I verified that the original solution does have the UTF-8 bom but once I install the template and try to create a solution from it, all the files get installed with utf-8 encoding instead of UTF-8 BOM. It is easier to fix but wanted to bring it up. I have code-analysis RULE: SA1412 turned on so if a consumer of the template creates the solution, by default they are not able to build the projects with success without fixing all the files with UTF-8 BOM.

Once again, thank you so much for such useful utility. Feel free to reach out to me if you have any questions or suggestions or comments on me using it incorrectly, please let me know.

Hi there,

First off, I just want to say that I love the solution you have here. Its definitely easy to set up and use!
Unfortunately, I've come across an issue when attempting to build the VSIX solution...

Once I open the project and try to build it, there seems to be several references missing e.g. EnvDTE, Newtonsoft.Json.
Luckily I've managed to add back was was missing using a combination of adding the references and using nuget packages.

Is this a normal part of the process?

I'm using VS2017 Professional if that is any help? I do have the VS extension dev pack installed

If any custom local images are referenced in the given overview.md they should be included in the publishManifest.json and copied to the VSIX project directory.

See https://docs.microsoft.com/en-us/visualstudio/extensibility/walkthrough-publishing-a-visual-studio-extension-via-command-line?view=vs-2019#asset-files

Hello.

Any chance to get this for VS2022 and .net 6?

It is nice to give different example script for PowerShell in the ReadMe

There is no reason it shouldn't.