Posts Tagged “Visual Studio”

I L.O.V.E. developing on my 15” MacBook Pro, but I had some fiddling to get it just right. ... [Read More]
I seriously love my Windows Phone… except for the availability of apps. ... [Read More]
One of the most common issues I am finding with teams moving from Team Foundation Version Control to TFS-Git is that they are including files in their repositories that they shouldn’t. The most common offenders are .suo user settings files, Nuget packages and Azure publish settings.   Luckily, the solution is straightforward.   1. Ensure you have no pending changes. 2. Close the solution 3. Go into Team Explorer and click Settings      4. In the Settings tab select Git Settings      5. Open the .gitignore file from GitHub that is specific to Visual Studio projects and copy the contents to the clip board. https://raw.githubusercontent.com/github/gitignore/master/VisualStudio.gitignore Figure: the .gitignore includes a list of all of the files that you want to avoid committing to your repository    4. In Settings | Repository Settings, click the Edit link next to ‘/,gitIgnore’        6. Paste the contents of the .gitIngore from GitHub into the .gitignore file and Save it.      7, In Team Explorer, navigate to the Changes window. Enter a comment and click Commit.      8. Click the Sync link to take you to Unsynched Commits      9. Click the Sync button to push your updated .gitIgnore      10. If you have included files in your repository that you wish to exclude from the repository but not delete from your local working directory refer to Remove files from your repository (so that they aren't tracked), but leave them in the working directory on my page for... ... [Read More]
If you are a ReSharper user (and you should be), check out the new dependency graph. It is awesome for easily getting a high level view of the dependencies between projects and layers in your solution. Figure: ReSharper 8 introduces a dependency graph to its architecture tools.     Figure: I structure my solution to reflect the Onion Architecture. http://rules.ssw.com.au/SoftwareDevelopment/RulesToBetterMVC/Pages/The-layers-of-the-onion-architecture.aspx I have layers for UI, Business Logic Interfaces, Repository Interfaces and the Domain Model. I then inject my dependencies into these layers.I like to structure the dependencies under a different solution folder so as to emphasise that the dependencies exist outside of the application core.     Figure: R# now generates a dependency graph of your solution (or a selected part of your solution) and by default groups the projects by Solution folders. I love this because with a few clicks I can get a very clear idea of the dependencies between the different layers in my solution, and see where references exist to dependency projects. I unselected three items to remove noise from the diagram: the Solution Items folder (which contains the deployment project and documentation), the Common folder (which contains cross-cutting concerns) and the Dependency Resolver project which configures the IOC container.     Figure: I generated the ReSharper dependency diagram as preparation for the first Sprint Review meeting and immediately noticed a dependency from my Client (UI) layer to a ‘Dependency’ project. No No No No No !!!     Figure: We refactored to inject the dependency... ... [Read More]
Git - Essential Commands for Visual Studio Developers ... [Read More]