Wish all blog readers and followers the Merriest Christmas of them all!
Doug Ortiz's Blog Architecture and Development blog postings of technologies ranging from Artificial Intelligence, Machine Learning, Large Language Models, PostgreSQL, Cloud, DevOps, Big Data, Data Science, Business Intelligence and Databases
Recently, I came across a blog posting that a T-SQL Script that generates a Christmas Card. It is the best one I have encountered yet.
Hope you enjoy it as much as I have:
If you have had the chance to download either SharePoint Foundation 2010 or SharePoint 2010 it is most likely that you have attempted to install with a local account on a Single Server Install. Odds are you have probably gotten disappointed because the wizard did not allow the installation with a local account. You were not the only one disappointed, although that disappointment did fuel the need to find a solution.
After some research, I did find a useful blog posting from the field that had the exact solution to my dilemma. The solution consisted in using PowerShell and a script named: “New-SPConfigurationDatabase”; this script is to be executed through the SharePoint 2010 Management Shell.
The step-by-step process would be like this:
1- Open the PowerShell Management Shell
Entering the prompted items:
DatabaseName
DatabaseServer
FarmCredentials
Passphrase
The process will take a while, when completed the cursor will appear in the command line.
2- Open the Configuration Wizard
Click Next Button
3- Restart the Services
Click Yes Button
4- Leave the Do not disconnect from this server setting selected
Click Next Button
5- Continue the normal course of the Configuration Wizard
There you go, now you have a Single Installation Server with a local account, this will work for both SharePoint Foundation 2010 and SharePoint 2010.
The details regarding SharePoint 2010 have long been awaited and while many have listed or blogged about it, this a compilation of many of these changes and enhancements.
While it is not in depth, it can be expanded with your comments and suggestions; feel free to leave comments so that we can improve upon this list.
Thank you for attending the presentation at the Rocky Mountain SharePoint User Group, as promised enclosed you will find the slides and the sample code.
Managing Techniques for Site Columns and Content Types - Slides
Managing Techniques for Site Columns and Content Types - Code
Almost everyone nowadays has or should have an Antivirus on their computer. The available choices usually come in the form of: free or purchased. While most of the time the free versions would not be as great as the purchased ones, a new contender is now available and no longer in Beta from Microsoft, this new product is named: “Microsoft Security Essentials”.
The purpose of Microsoft Security Essentials is to protect against:
So far it is very impressive, quick and simplifies the whole process; not to mention that it even has some nice videos available for: installing, scanning and fixing problems.
Recently, I was asked if I had an idea of how to resolve this problem; the most common and easiest solution to fixing this problem is to add the site to the Trusted Sites in Internet Explorer; while this is the easiest way to fix the problem, some of the users might not like the fact that they will have to do this the first time they access the site.
The second method to fix this problem is more involved and requires the modification of the master page, the steps for achieving this are listed in great detail in the following article:
Recently I was asked an excellent question:
“How do you update the templates contained in the Document Libraries of the ‘Case Management’ Site Template?”
It is a great and common question, the quick technical answer is:
“Update the document in which the Content Type of the Document Library is derived from”
Instead of keeping the answer technical thought a quick Hands on Lab would easily illustrate and answer much easily, with that in mind what you will need to complete this quick lab is:
· A site based on the “CaseManagement.stp”
· Office 2007 as the default Office Suite
· Around fifteen minutes to complete this lab
· For the purposes of this lab we will use:
o Document Library: Case Documents
o Document: Expense Report.xls
o Content Type: Expense Report
1. Ensure enough permissions to modify the Case Documents Document Library, administrator permissions should work fine
2. Navigate to the Case Management Site
3. Navigate to the Case Documents Document Library in which you wish to change the template
4. Click on the Expense Report WorkSheet
5. Select the Edit Radio Button
6. Click the OK Button
7. Modify the Expense Report Worksheet to match your needs
8. Save it to the Desktop or a location of your choice
9. Click the Settings Link of the Document Library
10. Click the Document Library Settings Link from the list of choices of the DropDown
11. Under the Content Types section click the Expense Report Content Type
12. Click the Advanced settings link under the Settings section
13. Select the Upload a new document template Radio Button
14. Click the Browse… Button
15. Locate the recently modified Expense Report Worksheet
16. Click the OK Button
17. Navigate to the Case Documents Library
18. Click the New Link
19. Click the Expense Report Link from the choices in the DropDown
20. Click the OK Button
21. The updated template is now displayed
22. Congratulate yourself, you did a great job!
Conclusion
After you complete the lab, you might be wondering:
“Do I have to repeat these steps for all the templates I wish to update?”
The answer is:
“Yes”
You might also end up wondering why so much complexity has been added to a simple process, the reason for this is because it does add tremendous flexibility when sharing this same template across your entire Site Collection.
Imagine that this template will be used all across the entire Site Collection which encompasses 50 Sites and dozens of Document Libraries, making a modification to a centric Site Content Type does simplify the entire process of maintenance. Mostly, because you make the modification and it will replicate across the entire Site Collection. One thing to keep in mind is that it will modify all those new documents based on the recently updated template only, in other words it is not a retroactive process; previously created documents will not updated the change.
Enjoy updated the templates!
La mayoría de la comunidad de SharePoint espera ansiosamente información relacionada a SharePoint 2010. Con esto en mente, tengo un par de vínculos que les interesará:
Bastante información interesante.
Most of the SharePoint Community is eagerly waiting for any news related to SharePoint 2010. That said, I do have a couple of links related to SharePoint 2010:
Lots of interesting information, enjoy!
Este artículo menciona una encuesta official de Microsoft en la cuál los ganadores serán elegibles a ganar una copia gratis de Windows 7 Ultimate. La idea de la encuesta es que Microsoft desea saber cómo buscan información relacionada a Windows 7.
La encuesta está disponible en www.surveymonkey.com y solamente necesitan contester 4 preguntas simples.
Ya terminaron de llenar la encuesta? Sino nada pierden con probar.
This article mentions of an official Microsoft hosted survey in which the winners will be eligible for a free Windows 7 Ultimate. The idea behind the survey is that Microsoft would like to know how you find information about Windows 7.
The survey is hosted on www.surveymonkey.com and you have to fill in 4 simple questions.
Have you submitted your survey already? I know I have.
Varios usuarios de PC han estado utilizando Windows 7 cómo su Sistema Operativo Principal; de hecho muchos han hecho el saldo de Windows Vista hacia Windows 7 Beta o RC. Esto dicho, pensé que listaría algunos problemas que encontré durante el upgrade a Windows 7:
32 Bit | 64 Bit |
La mayoría del software funcionó sin problema despues del upgrade, algunos fueron removidos porque era pre-requisito para el upgrade | |
Las licencias de software que fué comprado requirieron re-ingreso | |
Webcam fué reconocido y funciona perfectamente | Webcam no fué reconocido a pesar de que había sido instalada antes del upgrade |
Webcam requirió instalación antes del upgrade | |
Upgrade sin dificultad de Windows 7 Beta a Windows RC | Aún no ha sido puesto a prueba |
A pesar de Windows 7 estar aún en Beta y ahora en RC; casi listo para RTM. Estos problemas son relativamente mínimos comparados a previas versions de Windows.
Pensé que esta lista sería útil cómo referencia si están a punto de migrar a Windows 7.
Many PC users have been enjoying Windows 7 as their main Operating System; in fact most people have made the leap from Windows Vista into Windows 7 Beta or RC. That said, thought I would share a few hiccups that have encountered during the upgrade to Windows 7:
Windows 7 - 32 Bit | Windows 7 - 64 Bit |
Most software has been upgraded without a problem, some were requested to be removed The keys for Purchased software the keys had to re-entered | |
Webcam was recognized and fully functional | Webcam was not recognized even if installed prior to upgrade |
Webcam had to be installed prior to upgrade | |
Seamless upgrade from Beta 7 to RC | Have not tested yet |
Even though Windows 7 is still in Beta and now in RC; almost about for RTM release. These problems are relatively minimal compared to prior versions of Windows.
Thought this might come in handy for a reference if you are about to do the leap into Windows 7.
If you have been developing with SharePoint, you have probably noticed that not much is mentioned when it comes to developing mobile applications. An interesting approach is now available by means of using a Framework for SharePoint and Mobile Applications. This new Framework is named: Mobile Entree.
It is a framework that looks very promising. While it is not a free, it does add simplify mobile development quite well. You do not have to take my word for it; in fact you should go ahead and take a look for yourself.
There is available a 3 part series tutorial at: http://www.mobileentree.com/forums/yaf_postst8_What-is-Mobile-Entr233e-A-3-part-series.aspx
The tutorials cover:
Go ahead and take a look at it, it will be worth your time.
Para todos ustedes que han estado utilizando Windows 7, recientement el kit de entrenamiento para Windows 7 RC fue hecho disponible. El kit busca cómo audiencia todos aquellos que desean incorporar todas las características de Windows 7 en sus aplicaciones.
Antes de que lo instalen en sus máquinas, tengan en cuenta que necesitan cómo pre-requisito tener Visual Studio 2008 instalado.
El kit cubre los siguientes temas
Que esperan?
Procedan y descarguenlo en: http://www.microsoft.com/downloads/details.aspx?FamilyID=12100526-ed26-476b-8e20-69662b8546c1&displaylang=en
For all of you that have been enjoying working with Windows 7, recently the Windows 7 RC Training Kit for Developers has been released. It is aimed for all those who wish to make their applications leverage the Windows 7 Operating System.
Before you go ahead and install it on your main current machine, keep in mind that one of the requirements is to have previously installed Visual Studio 2008.
The training kit delves into the following features
So what are you waiting for?
Go ahead and download it at: http://www.microsoft.com/downloads/details.aspx?FamilyID=12100526-ed26-476b-8e20-69662b8546c1&displaylang=en
Interesting new developing for Groove, according to the Groove Team Blog groove is being renamed to SharePoint Workspace 2010.
Quite a few changes:
For more details go to: http://blogs.msdn.com/groove_development_team/archive/2009/05/13/makeover-for-groove-sharepoint-workspace-2010.aspx
I wanted to take a moment to thank all the readers which have contributed to this blog, their comments have been very useful. In fact, this posting is related to a particular situation that many SharePoint Administrators or Site Administrators might encounter when using SharePoint Lists or Document Libraries. The particular situation is when you are using a List or a Document Library to provide data to other depending Lists, Document Libraries, Content Types, etc. It even applies to Site Columns which are a useful way to provide data within your portal.
In order to prevent Items to be deleted from a List or a Document Library, a few things must happen first:
All these technology terms sound overwhelming, so let's stop for a moment and explain briefly what we are talking about here. In Windows SharePoint Services 3.0 and MOSS 2007, Lists and Document Libraries have a variety of events that are fired when an Item is processed; to mention a few of the most important ones:
For a complete list go to: MSDN - Event Fundamentals
Making it simple, we can specify code that will be processed when any of these events happen. This code to executed must be deployed to the GAC ( Global Assembly Cache ), once it is there the next step is to communicate to SharePoint by indicating the following:
To illustrate this process you will find the following two projects at www.codeplex.com/illustris :
These must be downloaded and extracted. Complete the following steps prevent the deletion of items on a desired SharePoint List or Document Library:
Ensure you have access to the Visual Studio SDK Tools
Once all these steps are completed successfully, any user who is not a Site Administrator will not be able to delete an Item.
Understanding the code
You are probably wondering what is really happening behind the scenes, and this is the explanation:
When you install the Demo.ProcessItemDeletion.dll Assembly:
public override void ItemDeleting(SPItemEventProperties properties)
{
base.DisableEventFiring();
if (!properties.OpenWeb().CurrentUser.IsSiteAdmin)
{
properties.Cancel = true;
properties.ErrorMessage = "Items cannot be deleted from this list.";
}
this.EnableEventFiring();
}
This code does the following:
When you click the Add Button the following code is executed:
SPSite oSite = new SPSite(txtSite.Text.ToString());
SPList oList = oSite.OpenWeb().Lists[txtList.Text.ToString()];
oList.EventReceivers.Add(SPEventReceiverType.ItemDeleting, txtAssemblyName.Text.ToString(), txtClassName.Text.ToString());
oSite.Dispose();
This code does the following:
Opens the URL specified in the TextBox
Opens the List or Document Library specified in the TextBox
Communicates to SharePoint and tells it to execute the code in the previously installed assembly when the ItemDeleting Event is fired
Where to go from here?
That really depends on you, mostly because you can expand this code and make it more functional. For instance, you could provide a more detailed explanation of why the user could not delete the item. Or maybe you want to apply the same idea to updating items as well ( which would require the development of code in the Demo.ProcessItemDeletion project for the ItemUpdating Event ).
The whole purpose of this posting is to ignite ideas that will help you customize your portal to better fit your needs.
By popular demand, I am dedicating this posting to the avid readers of the blog.
As mentioned in the title, we will be addressing how to display and filter ListItems contained in another SharePoint Site by using SharePoint Designer 2007.
This is a very easy way to maximize the use of a powerful tool such as SharePoint Designer 2007 is for SharePoint Technologies. Now, let's start customizing:
While this approach easily accomplishes the tasks of displaying and filtering a SharePoint List from another SharePoint Site, it can become an inconvenience for a SharePoint Administrator in a scenario in which multiple sites will require a specific filter for the SharePoint List.
Enjoy!
Tom Clarkson uploaded on March 11, 2008 a new release of WSPBuilder.
In a previous blog posting we quickly glanced at WSPBuilder, with this new Release 1.01 there are a few niceties added:
Besides the WSPBuilder Project and WSPBUilder Project with Workflow Templates available for Visual C#, a new one has been added:From Doug Ortiz's Blog
When Right-Clicking the project two new additional task items are available:From Doug Ortiz's Blog
I encourage you to download and review the features of WSPBuilder.
WSPBuilder Extensions 1.01 is available for download at: http://www.codeplex.com/wspbuilder.
There are more details regarding the new additions by click on the Releases Tab on codeplex.
Displaying Concatenated Columns in a Calendar View
Sometimes, the need to display columns that contain values from other
existing columns in a SharePoint List arises. For those times, a quick and easy
solution is to create a calculated column that will contain the columns we desire
to display.
A real world example for using a Calculated Column that comes to mind is in a
Calendar View ListItem: Merging the Title Column with the Date and Time of the ListItem.
This can easily be accomplished by creating a calculated column that concatenates the
values in those columns.
For this example, we will assume you already created a standard Calendar List. Under the
Calendar List Settings of your List:
=Title & " " & TEXT([Start Time],"mmm-dd-yyyy")
In order to displaying the newly created TitleAndDate Column in the Calendar View, we
must modify the Calendar Columns View and set:
DropDowns to: TitleAndDate
The end result will display the Title and the Start Date separated by a space.
Before
| After
| ||||
Reviewing the Formula
The magic occurs in the TEXT function that converts the Start Time Column into text,
followed by the text being formatted into "mmm-dd-yyyy".
In case you need to add the time, just replace "mmm-dd-yyyy" with "mmm-dd-yyyy HH:MM:SS".