UPDATE: This is supported with the new execution engine, available in BuildMaster 4.9. As of BuildMaster 4.6, this isn't supported, but definitely something we will support in the future. I can see other cases where this would be useful as well (e.g., copying files or deploying artifacts to multiple target servers).

This sort of workflow isn't really support; the standard way to do this is to re-execute a previous release's promotion to Production, thereby setting the context for the artifact to that of the previous-deployed build.

You should be able to reference your library from your custom extension. You just need to make sure that it and any other dependencies are either included in the .bmx file or are installed to the system GAC. BuildMaster doesn't use EF, so there shouldn't be any version conflicts there.

Note: we have now scheduled this feature for v3.6

A patch is available below; run the contained SQL scripts against the BuildMaster database in any order to resolve this. Note that this fix only applies to v4.6.3-4, and will be included in v4.6.5: http://44.inedo.com/buildmaster/CloneAppPatch-v4.6.4.zip

The story continuous :) Because I set TeamCity to create source packages as well (it's a checkbox called: Include sources and symbols) it was overwriting the packages in ProGet (I have all the PDB and sources in my nuspec files as well). This was causing the issue with the config file being gone, because TeamCity strips those files out for the symbols packages. So... I was doing things twice... Must be user error ;)

Which older version of nuget works correctly?

VPN will occur at a much lower level than ProGet operations (which is HTTP/IIS), so I suggest you use a tools like Wireshark to dig a little further and see where the problem might be.

4.0 is available for download now; we've tested it about as far as we can, the main reason it's still considered "beta" is to see how the Docker/installation process works in the wild. So, please give it a try. Depending on the requirements of non-AD LDAP, if it's easy to do, we can implement it quite soon.

Hi Dean Restarting the ProGet service solved the problem. Thanks!

It seems to be more stable now, or I can at least see the NuGet page on ProGet. Thanks.

All of our installers are signed, our build process is isolated, and we do frequent network scans -- so it's definitely not a virus. If you want to verify it yourself, you're welcome to use a tool like .NET Reflector; it's just managed code and is not obfuscated in any way. It's just a self-contained SQL change script distribution package generated by our BuildMaster product. Still, every once in a while we get some part of the installer flagged by an AntiVirus scanner. Usually it's bmdbupdate.exe, since that does some "questionable-looking" things to an antivirus engine, such as embedding its dependency assemblies as resources. Please let them know about the false positive; the more people who do, the greater the chance they won't flag these in the future. Thanks for letting us know!

It's not recommended to check-in the modified assemblyinfo.cs file. For a few reasons, including the one you identified: it causes issues with source control related to the build. But moreover, attributes in AssemblyInfo.cs are metadata more than code; in other platforms (like Java) these are always added as part of the build process.

Hi Dean, Sorry I continued trying and found out the problem was caused because I had to include the -k flag (for HTTPS) and to include the username and password in the URL. Problem solved. Thanks. Kevin

As per email response: Try upgrading to 3.6.5 first, then to 4.6.4.

As of 3.5, these are the features not available in the free edition: Active Directory / LDAP Integration Filter Packages by Name & License Load Balancing & High Availability Granular Privileges & Security (scoping by individual feeds) MyGet Feed Sync

Thank you for the cache tip. I've included -NoCache modifier to a command, and ProGet asked me about credentials.

You can just back-up the database, restore it on the new server, and edit the connection strings in the appSettings config files for the web and service.

I'm not sure what the tool is validating exactly, but after uploading the WSDL file to https://www.wsdl-analyzer.com, it said the document was valid. I am not super familiar with Java or any Java tools, but the same problem looks like it has occurred here: http://stackoverflow.com/questions/13499860/jax-ws-error-on-wsdl-file-error-resolving-component-sschema