Deployment Tools for Sharepoint | ||
stsdev | generate Visual Studio project files and solution files to facilitate the development and deployment of templates and components for the SharePoint | |
Wspbuilder | WSP) creation tool for WSS 3.0 & MOSS 2007 | |
SPVisualDev | to develop features and artifacts with Visual Studio 2008 and many more features | |
Share Infopath Forms | Makes infopath forms deployment easy | |
Manage configuration modification feature | Feature to manage the configuration modifications |
Thursday, June 24, 2010
Deployment Tools for Sharepoint
Wednesday, June 23, 2010
MOSS Standard DevelopmentTools
Standard Development Tools for Sharepoint
| ||
Reflector
|
Explore and analyze compiled .NET assemblies, viewing
them in C#, Visual Basic, and IL | |
GhostDoc
|
free Visual Studio extension that automatically
generates XML documentation comments for methods and properties based on their type, parameters, name, and other contextual information | |
DumySMTP
|
Command line utility that simulates a
smtp server. | |
CAML Query Builder
|
will help in build, test
and execute CAML Queries | |
Fxcop
|
is a free static code analysis tool
from Microsoft that checks .NET managed code assemblies for conformance to Microsoft's .NET Framework Design Guidelines | |
SPdisposecheck
|
help you to check your assemblies that use the SharePoint API so that
you can build better code. It provides assistance in correctly disposing of certain SharePoint objects to help you follow published best practice. This tool may not show all memory leaks in your code | |
Resource Refactor
|
easy way to extract hard coded strings from the code
to resource files | |
SharePointLoggingSpy
|
allows real time diagnostics of multiple servers in a sharepoint farm using a single console view
| |
WSS/MOSS Log file reader
|
View, search and filter SharePoint ULS log files
directly from within Central Administration | |
AD Explorer
|
use AD Explorer to easily navigate an AD database
| |
XML NotePad
|
provides a simple intuitive user interface for
browsing and editing XML documents | |
WinDiff
|
Graphical file comparison tool similar to Beyond
Compare | |
SharePoint Data Population Tool
|
a capacity planning and performance testing tool that populates
data for testing SharePoint deployments. | |
Resharper
|
provides solution-wide error highlighting
on the fly, instant solutions for found errors, over 30 advanced code refactorings, superior unit testing tools, handy navigation and search features, single-click code formatting and cleanup, automatic code generation and templates, | |
Snippet Compiler
| ||
Sandcastle help File builder
|
used for creating MSDN-style documentation from .NET assemblies
and their associated XML comments files. | |
Sandcastle
|
Documentation compiler for managed assemblies
| |
CKS
|
is a set of best practices, templates, Web Parts,
tools, and source code | |
Fiddler
|
to inspect allHTTP(S) traffic,
set breakpoints, and "fiddle" with incoming or outgoing data | |
Procmon
|
Process monitor tool
| |
Stsadm.webconfig
|
Make SharePoint web config
modifications using a config file, rather than having to hard-code static strings in a class file | |
MOSS Feature Generator
|
includes Site Columns, Content Types and ListTemplates (including schema.xml
and forms) | |
allows a developer to explore the scopes and managed properties of a
given SharePoint Search SSP. Also builds queries in either Keyword or SQL Syntax, submit those queries and examine the raw web service results |
Thursday, June 3, 2010
How to update items without changing Modified/Modified By
When there are some operations or a clean up to be done on sharepoint site by a system account using a tool then there is always a constraint that it should not leave its traces. I mean the changes should reflect leaving the modified and modified by column values as it is.
So in this case the method SPListItem.Update() should be replaced by SPListItem.SystemUpdate() and followed by SPList.Update() always.
This way the lisitem will not get a new version created but to the existing version with the changes that you have currently and hence no change in Modified and Modified By columns.
How to handle the checkedout items when modifying Sharepoint Listitems
Im sure you might not get what this post is all about by just looking at the title, so i give you with the scenario you might be into and then you can go through the complete post
scenario :
I have a requirement for a tool that should update the metadata(sitecolumns value) of the document library/list items programatically.Everything is pretty clear except about the items that are checked out, that you get when you ponder ;-)
I can get the tool in fly if i ignore the items that are checkedout. So how to deal with the checked out items?After digging into the setttings of the library i thought disabling the version settings would do the trick but i get only the error "you cannot edit the properties when the document is checked out" when trying to edit the items that are already checked out by other user
Though after using the method SPListItem.SystemUdpate() i can do nothing about the checkedout items. More strategically im left with the only option to run the tool/code untill there are no checkedout items i.e i got a scheduled timer job that will run this code/tool untill no checkedout items.
Plz let me know if there is something else that you got working.Thanks!
P.S more about SPListItem.SystemUpdate() here.
Get loginname of the Sharepoint user with username efficently
If you wonder how to get login name with user name programmatically in SharePoint then you are reading the right post.
We can do this by looping all the users of web and get the spuser that matches with the username or by simply using SPFieldUserValue like below,
using (SPSite site = new SPSite("http://sharepointcustomization.blogspot.com/"))
{
using (SPWeb web = site.OpenWeb())
{
SPFieldUserValue userValue = new SPFieldUserValue(web, "UserName");
if (userValue.User.LoginName == web.CurrentUser.LoginName)
{
//do something!
}
}
}
using (SPSite site = new SPSite("http://sharepointcustomization.blogspot.com/"))
{
using (SPWeb web = site.OpenWeb())
{
SPFieldUserValue userValue = new SPFieldUserValue(web, "UserName");
if (userValue.User.LoginName == web.CurrentUser.LoginName)
{
//do something!
}
}
}
Subscribe to:
Posts (Atom)