Abstract levels container

If you have problem connecting to MSSQL$Microsoft##SSEE instance after installing SharePoint Services 3.0, check if Windows Internal Database (Microsoft##SSEE) is really installed (should be in services list and Add/remove programs).

If its not installed try this:

1. Run regedit,
2. Go to HKLM/Software/Microsoft/Shared Tools/Web Server Extensions/12.0/WSS/ServerRole,
3. Change SINGLESERVER value to WFE,
4. Run SharePoint Products and Technologies Configuration Wizard again,
5. All should work now.

References:

• http://social.technet.microsoft.com/

Tools SharePoint Services

When a user installs an alert she receives an email “You have successfully created an alert for …” but alerts aren’t being sent from SharePoint.

Solution:

run stsadm.exe:

stsadm.exe -o setproperty -url http://mywss30server/mysite -pn alerts-enabled -pv true
stsadm.exe -o setproperty -url http://mywss30server/mysite -pn job-immediate-alerts -pv "every 5 minutes"

Resources:

• WSS FAQ
• Alerts Not Working – John Bailo
• social.technet.microsoft.com

Tools SharePoint Services, WSS

Requirements

1. A Java runtime – needed to run FitNesse .
2. The srvany.exe and instsrv.exe from the Windows 2003 Resource Kit.
3. An account on the machine that has Log On As Service rights and full rights to the directory where FitNesse runs and keeps its files.
4. The .NET Redist if you want to use the .NET version of the FitNesse server.
5. An account with access to the machine to install it on and sufficient rights to do that – this usually means local administrator rights.

Installing FitNesse as service

1. Install FitNesse :)
2. Install Java
3. In FitNesse root folder find start.bat theres something like this:

   java -cp fitnesse.jar fitnesse.FitNesse -p 8080

   where -p is port number. You should start it and check if under http://localhost:8080 runs your installed FitNesse.

4. Install Windows Resource Kit (or srvany.exe and instsrv.exe only)
5. Install new service:

   instsrv.exe FitNesse "<path to the srvany.exe file>\srvany.exe" -a AcoountName -p AccountPassword

6. Add AccountName account required rights (modify) to FitNesse folder
7. Create file FitNesseAsService.reg:

   [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FitNesse\Parameters]
   "Application"="C:\\Program Files (x86)\\Java\\jre6\\bin\\java.exe"
   "AppDirectory"="<path to the FitNesse folder>\\FitNesse"
   "AppParameters"="-cp fitnesse.jar fitnesse.FitNesse -p 8080"

   and run it. This will add required keys to the registry.

8. And thats it. If you want to remove FitNesse service, run this:

   instsrv FitNesse REMOVE

9. You can uninstall Windows Resource Kit (save instsrv and srvany if you want).

Source

http://fitnesse.org/InstallingFitNesseAsaService

Development, Tools FitNesse, HowTo, Testing

Spis narzędzi przydatnych przy projektowaniu stron www i nie tylko: http://ui.blox.pl

Development, Tools Usability

Whole process looks very simple: grab VSS, produce text file, run SVN and consume produced file.

1. Download and install (unpack) vss2svn
2. Run vss2svn.exe

   vss2svn.exe --vssdir \\vss\repository\path

3. That will produce

   vss2svn-dumpfile.txt

   file which will be consume by svnadmin

4. [Optional]: compress and send vss2svn-dumpfile.txt file. I’m using 7-zip:

   "{PathTo7-Zip}\7-Zip\7z.exe" a "%DATE% vss2svn-dumpfile.7z" "vss2svn-dumpfile.txt" -t7z -mx9 -aoa

5. Run svnadmin, use vss2svn-dumpfile.txt

   "{PathToSVN Server}\VisualSVN Server\bin\svnadmin" load "E:\SVN Repositories\BackupVSS" < "vss2svn-dumpfile.txt"

6. And thats it.

Whole script might look like this:

E:
CD E:\Vss2Svn\
vss2svn.exe --vssdir \\vss\repository\path
 
:: ### Optional compression, you might do this if you want send file somewhere else ###
"C:\Program Files (x86)\7-Zip\7z.exe" a "%DATE% vss2svn-dumpfile.7z" "vss2svn-dumpfile.txt" -t7z -mx9 -aoa
 
:: ### SVNAdmin ###
"C:\Program Files (x86)\VisualSVN Server\bin\svnadmin" load "E:\SVN Repositories\BackupVSS" < "vss2svn-dumpfile.txt"

Tools HowTo, Subversion, SVN, Visual Source Save, VSS

Error: The specified metadata path is not valid. A valid path must be either an existing directory, an existing file with extension ‘.csdl’, ‘.ssdl’, or ‘.msl’, or a URI that identifies an embedded resource.Source: forums.microsoft.com

ADO.NET Entity Framework

OS: Vista x64

Platform: VS 2008

The catch is that apparently the designers are not supported on 64-bit machines. You should copy two files from %windir%\Microsoft.NET\Framework64\v3.5 to %windir%\Microsoft.NET\Framework\v3.5:

• Microsoft.Data.Entity.Build.Tasks.dll
• Microsoft.Data.Entity.targets

then restart Visual Studio and rebuild your solution.

Tools ADO.NET, Entity Framework, Problems, Visual Studio 2008

Error: The selected file is not a valid solution file.

Platform: VS 2008

Description: When one trying to use VisualSourceSafe 2005 with VisualStudio 2008 one get above error.

Solution:

• First install Visual Source Safe 2005 Update CTP
• Next run as administrator the following command: regsvr32 “%programfiles%\Microsoft Visual SourceSafe\tdnamespaceextension.dll”

Source: http://blogs.msdn.com/richardb

Tools Problems, Visual Studio 2005, Visual Studio 2008