|
|
|
|
Latest entries in the Euricom Team blog
|
|
|
|
|
Author: |
Euricom |
Created: |
4/2/2009 1:35 PM |
 |
|
The idea of this blog is to share knowledge and experience from our .NET specialists with all the .NET Geeks out there! |
By Euricom on
9/4/2009 2:38 PM
A lot of times you see developers writing code that, in order to read it, you have to scroll half an hour to the right because one line of code contains like a thousand characters. To (try to) avoid this, you can add a registry setting that displays a line in a specific color and at a specific position to indicate a marker for the desired maximum line length in the Visual Studio Text Editor.
By Kurt Torfs, .Net Solutions Architect
Read More »
|
By Euricom on
8/28/2009 9:14 AM
Previous Chapter: Part 8 - The Management
So what do you do when you have decided that SharePoint is for you? How do you get started? In this chapter I’ll try to provide an answer to those questions. But I have to issue a warning here. This is one view, an opinion that, although fueled by experience, might still not be the ideal way for you and your company or department. We won’t go into too much detail so the “solution” stays as generic as possible and therefore as widely applicable as possible.
Typically, since it is a server product, SharePoint is treated like other Microsoft server products. You install it, configure it and start working with it. Wrong! I can guarantee you that if you do this, after six months, you will have a very big SharePoint environment, but nobody will be able to work with it or find anything on it. No, what you should do it treat it as an application development and that starts with … analysis.
By Ronny Gabriels, Functional Analyst and ex-.net Solution Architect
Read More »
|
By Euricom on
8/27/2009 9:38 AM
Previous Chapter: Part 7 - The Documents
I think from all the chapters before this one, it’s pretty clear that SharePoint can really help you and your department. The thing is that if you are not already working with a system like this, there will always be people reluctant to use it. Because change is change and some people just don’t know how to deal with that. Especially when you have a very diverse group of people in your department ranging two maybe even three generations, there will be those who see it as a new toy and does who see it as an obstacle. That’s where you as a manager can make the difference. A lot of the work convincing people of the benefits and strengths will feel, and actually be, an internal marketing campaign. Something you might even want to spend some money on, since the benefits will increase exponentially with the number of people using it. Collaboration and communication only works if almost everybody uses it and uses it correctly. You can compare it to the telephone network. What good would it be if you could only reach 50% of your friends through it? The success, just as it will be with SharePoint, lies in the fact that everybody can be reached through it.
By Ronny Gabriels, Functional Analyst and ex-.net Solution Architect
Read More »
|
By Euricom on
8/11/2009 2:05 PM
Yesterday I’ve installed a new TFS 2010 Beta 1. Everything was working well from the first time, but we could only access the server with his local name. Our developers work both at the office and at home, so we wanted to enable a (public) fully qualified domain name. The TfsAdminTool seems to be gone so I couldn’t configure the connections like I did with TFS 2008. I couldn’t find either a simple solution but the following procedure did the job. (Without reinstall TFS)
By Wim Van Hoye, Technology Manager
Read More »
|
By Euricom on
7/15/2009 9:54 AM
Previous Chapter: Part 6 - The Knowledge Base
Every department in every company in the world is going to have to deal with documents. Where a long time ago, this was all done on paper – and yes I know that in some types of companies this is still the case – now most companies use digital documents. The big idea behind the digitalization of documents was that it would be a lot easier to share documents, work on them simultaneously with more than one person and store and archive them more easily.
The problems with the document digitalization quite rapidly followed the actual introduction. Because it was so easy to share, store, etc. all of a sudden a lot more documents popped up. Then came the version issues. Who was working on what version of the document? And then it was time for the storage issues. Where could you store all of these documents, and all of their versions, so that people could actually find them when they needed them?
Throughout the years there have been quite a lot of document management systems that tried to provide answers to these problems. All had their strengths, all had their faults. The biggest issues were that they focused solely on documents and where/are notoriously hard to integrate with other systems. Besides providing the standard document management answers, SharePoint now tries to provide an answer to the DMS problems too.
By Ronny Gabriels, Functional Analyst and ex-.net Solution Architect
Read More »
|
|
|
|
|
|