My blog has been moved to http://msmvps.com/blogs/laflour
On these long weekends I decided to look through the following book “Code Leader: Using People, Tools, and Processes to Build Successful Software”, that somebody recommended me recently, only for a single reason – a couple of years ago I planned to write the set of articles about the tools and approaches of the modern development process.
In this book author directs you through important aspects of modern software development process. He describes how process should be organized, which tools, libraries and patterns should be used almost for all projects. It’s not a guideline to follow, but a good sample of what to use and to support the process of development.
Book is written for those who are just stepping into Team Lead positions and want to understand the pillars of this role. Experienced guys won’t find a lot of useful stuff in this book. I’d say that book will be useful for those who have 3-5 years of development experience.
Book consists from 12 chapters and begins from the moment when project starts and guides you to debugging and error handling.
Chapter 1: Buy, Not Build
Chapter 2: Test-Driven Development
Chapter 3: Continuous Integration
Chapter 4: Done Is Done
Chapter 5: Testing
Chapter 6: Source Control
Chapter 7: Static Analysis
Chapter 8: Contract, Contract, Contract
Chapter 9: Limiting Dependencies
Chapter 10: The Model-View-Presenter (MVP) Model
Chapter 11: Tracing
Chapter 12: Error Handling
I would like to highlight the most interesting sentences in this book
Haven’t been updating my blog for several months, due to tough commitments to my SharePoint communities and online projects which will be released soon, and because nothing significant happened.
In these days Microsoft released Beta 1 of Visual Studio 2010 and there are a lot of things to mention. For these who missed the news and didn’t install it yet – go to MSDN and download Beta1 http://www.microsoft.com/visualstudio/en-us/products/2010/default.mspx
Visual Studio 2010 introduced several significant changes, for example the studio interface is build on the top of WPF, not the WinForms. Someone will find this attractive ,others, like me, might not be very inspired with such changes. I’ve seen the performance degrade in UI when you are using Visual Studio 2010 on slow PCs, which doesn’t have good video adapters.
There are new features in interface of in VS2010 like customized start up pages, multi-monitor support, windows remember their locations after being closed, extension manager for plugins and tools. See there info about new features http://blogs.msdn.com/jasonz/archive/2009/05/18/announcing-vs2010-net-framework-4-0-beta-1.aspx
C# language provided new features like dynamic objects and variant. More details in this link http://code.msdn.com/csharpfuture.
So, stay tunned and follow the #VS2010 hashtag in tweeter to get the latest updates http://search.twitter.com/search?q=%23VS2010
Btw, Visual Studio 2010 uses Consolas 10 font by default, start using in in VS 2008 to be ready for new look 🙂
PS: Don’t forget about the Visual Studio 2010 Forums http://social.msdn.microsoft.com/Forums/en-US/category/visualstudioprerelease
This guideline provides detailed overview of System.Web assembly and the new classes and methods in ASP.NET 4.0, which were released with Visual Studio 2010 Beta1.
Document is subject to change – we are trying to find detailed information about all new stuff and update description column. Send us your comments and suggestion via this online form.
ASP.NET 4.0 introduces several changes to the web assemblies and also merges several dlls that existed in .NET 2.0 – 3.5 SP1. For example, new features from ASP.NET 3.5 SP1 System.Web.Abstractions.dll and and System.Web.Routing.dll are merged with System.Web.dll, under System.Web namespace.
Beta1 of ASP.NET 4.0 introduced 27 new classes/interfaces/enums and 22 modifications of the existing ASP.NET 3.5 SP1 functionality.
Take into account, that Beta1 doesn’t provide the complete list of the new features – they can add new stuff or remove existed one prior to the final release.
The latest document version is available there http://tinyurl.com/qr583j (PDF file)
Previous 10 are published there
This month I’m reading my first SharePoint presentation in Sydney (Australia), so I welcome NSW ppl to come to listen to me and to criticize a bit 🙂
I’m planning to run about 3 presentations of “best practices” for SharePoint infrastructure and Development, so this one starts with the basis of how to create the SharePoint farm
Detail info below
|
‘Best Practices of SharePoint Farm Deployment’ Presented by Michael Nemtsev (MVP), Senior Developer – Readify
Wednesday 25 February, 6:00pm – 8:00pm | Cliftons, 190 George Street, Sydney
In this RDN session, Michael will highlight best practices of how to deploy and configure the SharePoint environment from scratch, covering different farm scenarios and providing practical instructions of how to generate a strong SharePoint baseline. …register now
Find out more about RDN or download the RDN Information Brochure (PDF). |
Topics are:
PowerPoint presentation is available to download in PDF format
The aggregated post of the first 10 posts from the “Do you know” SharePoint Tips series
I have several 10% discount vouchers on Microsoft Exams valid till March 31, 2009
Note that the limited time offer is valid in Australia ony and for Microsoft Certified Technology Specialist (MCTS), Microsoft Certified IT Professional (MCITP) and Microsoft Certified Professional Developer (MCPD) exams only.
If you want to get one drop me a word via “Contact Form” page
Mirror: Australia only discount vouchers for MS Exams. Ask me one
In this post I’d like to review existed tools for the SharePoint management. The idea to create this overview appeared after I read that Bamboo solution shipped their own SharePoint analyzer. The first I thought was – “Why do we need another tool, if we already have SharePointSpy and SharePointManager?!”
So, let’s start comparing of three tools, which exist on market
1) SharePoint Analyzer from Bamboo Solutions
2) SharePoint Manager from CodePlex
3) SharePointSpy from EchoTechnology
and how those tools functionality differs.
| Items | SharePoint Analyzer | SharePoint Manager | SharePointSpy |
| Farm setting | yes | yes | no |
| Farm servers | yes | yes | no |
| Logs for each sever in farm (IIS/SharePoint) | yes | no | no |
| Web App overview | yes | yes | yes |
| Web App on server | yes | yes | no |
| Central admin options | no | yes | no |
| Content DB site location | yes | no | no |
| AAM | yes | no | no |
| IIS settings | yes | no | no |
| Service instances | yes | no | no |
| Definitions export (list, content type) | no | yes | yes |
| Web Parts Gallery | yes | no | no |
| Account Security overview | yes | yes | yes |
| SharePoint DB overview | yes | no | no |
| Best Practices Analyzer | yes | no | no |
Results: analyzing those tools I found that SharePoint Analyzer and SharePoint Manager provide you the richest functionality to manage your SharePoint environment. I can’t name the best tool, because those tools have different target audience and must be used together.
SharePoint Analyzer from Bamboo solutions provides rich and good, structured overview of your SharePoint farm for administrator/infrastructure perspective – detailed info about servers, web applications, logs, and etc. Good usability, grouping and detailed information across all your farm servers, but there are few useful info for developers.
SharePointSpy is absolutely different tool – it stays away from infrastructure, providing your deep info about sites, features, site definitions and etc., allowing your to export different schemas xml. Really powerful tool for developers, who need deep dive inside SharePoint stuff.
SharePoint Manager locates between administrator vs developer poles. It provides you almost the same functionality as SharePointSpy, but has a lot of information for infrastructure guys/administrators as well.
My choice: combination of SharePoint Analyzer for maintenance and SharePoint Manager for development. But, if those three tools were shareware, then I’d chose SharePoint manager for its balance between admin and developer functionality.
I’ve seen several cases, when people use CQWP and surprises when it doesn’t return all items in standard mode and returns all necessary items in “edit” mode. I find this topic is not being documented enough anywhere.
So, CQWP ignores following items from your queried data:
Those scenarios are “behaviour by design”, and I found such behaviour logical. User’s are working on their items, and work in progress – you shouldn’t show such items
Workaround: set “UseCache” property to “false”.
Cite from SharePoint team:
“You are only seeing your items in edit mode because the caching infrastructure of the CQWP does not cache checked-out items of individual users and we disable cache in edit mode. You can disable caching on your Web Part by setting the "UseCache" property to false”
So, my recommendation is to revise your approach to return published and checked-in stuff only.
Mirror: Why Content Query Web Part (CQWP) doesn’t return all results.
 | Mr WordPress on Blog has been moved |
| live on “Code Leader” book review |
| chen on “Code Leader” book review |
| fasdf on Best Practices to plan and con… |
| dfasdf on CSS and ASP.NET Menu in S… |
Michael's Coding Den 