Tag: Git

Some of you have reported that you've been experiencing errors mentioning "getcp" when using Git Extensions for SalesLogix. This post will outline the problem and show how to fix it.

Whether you're using Git, or some other source control system, there are certain files in a SalesLogix model that you do not want to include in your source control. Many part of the files in an exported SalesLogix model are automatically generated by the Application Architect and by the build process when you build your web platform. Having these files under source control would only complicate things when working with multiple developers since you'd each need to merge these automatically generated files with each pull/checkout from source control since they change every time.

When using Git, or really any source control system, you don't want everything in your SalesLogix model to be under source control. There are some files that the Application Architect uses for it's own purposes and volatile files that have no importance for your purposes and are recreated as needed. These files that change often with no importance to what you're working on can make things difficult when working with source control since every time a developer pushes changes, that are pulled by another developer these files will need to be merged. Doing this every time will get old fast. Git has the built in ability to exclude files from source control. Let's take a look at how.

In the last post in the Git for the SalesLogix Developer series, I outlined how to set up a repository. Once that is complete, other developers can use that repository to collaborate on the project. This post outlines how to use a repository and bring it locally so you can use it for development.

If you've been following along in the Git for the SalesLogix Developer series, you should now have Git installed and configured. Now it's time to start putting it to use. In this post (and included video), I will outline the steps to take an existing SalesLogix project and put it under Git source control. Setting up the initial repository is not a hard task, but knowing all the steps is the only way to get it done.

In this second post in the "Git for the SalesLogix Developer" series, we will be taking a look at how to install and configure Git. This tutorial will give you everything you need to know if you are new to Git so you can get it all set up and ready to use. In a later post we'll look at how to use Git, but it all starts with knowing how to get started.

The first in a new series of posts on how to use Git for source control in SalesLogix development, this post will introduce Git, some Git terminology and some of the software you'll use.

I have released a big update for Git Extensions for SalesLogix. This new version includes a ClickOnce installer and will keep itself up to date automatically. The installation of Git Extensions for SalesLogix is now brain-dead easy. You just access a URL and click the Install button. Not only that, you'll automagically be updated to new releases as they become available.

For anyone who uses Git Extensions for SalesLogix, I've released a small update that adds some core functionality and makes it possible to complete the entire scenario of setting up and using Git with a SalesLogix project - all from within the SalesLogix Application Architect!

Yesterday I announced my new project Git Extensions for SalesLogix. I received a lot of e-mails from people who read that post, so I thought it would be a good idea to record a quick video so you can see it in action and get a better idea how it works. This quick 4-5 minute video will show you how to commit changes in Application Architect to a Git repository and push the changes to an online repository as well, all from inside Application Architect using Git Extensions for SalesLogix. You'll also get a peek at a few other pieces of functionality as well. All in all, if you already use Git Extensions then this will be a no-brainer to use. If you're new to Git, or to source control at all, then this will lower the learning curve significantly and make things much easier to get into.