Written by: Lee Kohn
I recently ran into an issue on one of my development ASP.Net servers where I would deploy an updated DLL (Dynamic-link library) to the GAC (global assembly cache) but the ASP.Net applications which referenced the DLL would throw compilation errors at run-time saying that newly added fields/methods were not present in the assembly. I tried uninstalling and re-installing the assembly, adding the new DLL to the bin, and referencing it from there and so on, but nothing seemed to work.
As it turns out, ASP.Net keeps a cached version of the JIT compiled DLL in the C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files directory that was being used instead of the new DLL which was in the GAC. To fix it, I simply deleted the contents of this folder and everything was right as rain!
-Lee
Written by: Johnny Bouder
This blog post will outline the steps required to upgrade a SharePoint 2007 Visual Studio Project to a SharePoint 2010 Visual Studio Project using the VSeWSS Import Tool for Visual Studio 2010 (http://archive.msdn.microsoft.com/VSeWSSImport). The tool is kind of old at this point, but it is still very useful and I haven’t found a better tool.
This post will be helpful to you if you have created custom SharePoint 2007 solutions using the VSeWSS Visual Studio extensions. The tool above can be used to easily upgrade these projects to SharePoint 2010 projects. This post should be especially useful if you are upgrading existing SharePoint 2007 sites to SharePoint 2010 that already have these Web Parts added and you would like the ability to add additional modifications to these projects.
Installing the VSeWSS Import Tool
The VSeWSS tool is actually provided as a Visual Studio Project, which needs to be compiled in order to build the executable to install the tool into Visual Studio. One other thing to note is that in order to open the solution in Visual Studio 2010, you need to install the Visual Studio 2010 SDK (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=47305cf4-2bea-43c0-91cd-1b853602dcc5&displaylang=en). Why this isn’t included in Visual Studio by default is beyond me. Or why it is not mentioned in the VSeWSS Import Tool installation instruction is also beyond me.
So basically, install the SDK, and then follow the instructions to install the new project type.
Importing Your Projects
To get started you want to copy any old Visual Studio project directories over to computer where you will be writing your Visual Studio 2010 solutions.
Once you have your old projects ready and have everything installed go ahead and fire up Visual Studio 2010. Click New Project and you will now have a new project template called Import VSeVSS Project (if the installation went well). See below:
Written by: Daniel Nguyen
The Department of State’s Tech@State team will be hosting the 5th edition of Tech@State events at the Jack Morton Auditorium in the Media and Public Affairs building of George Washington University on Friday May 27 and Saturday May 28. Over 200 attendees will “explore the mechanics of games, business and sustainability, design, education, international aspects, games for social change and much more.”
MetroStar Systems will be supporting the Tech@State team with our MyStanly twitter moderation/display application, and our CEO Ali Manouchehri is slated to speak on two separate panels on Day 1. He will first address the topic of “Games, Business and Sustainability” and then present with a panel about “Military and Government games”. The event features an impressive collection of government, academic, non-profit, and industry experts/tech innovators who will be sharing their experiences and exploring many aspects of serious games. The agenda and complete schedule is now available at the Tech@State blog.
Here are some additional URL links that may be helpful if you are interested in attending or want more information:
For those of you who cannot attend the event, you are in luck! This event will be live streamed on Tech@State’s UStream channel: http://www.ustream.tv/channel/tech-state. You can also follow the conversation on twitter by searching the hashtag #TechAtState and following our live tweets @metrostarsystem.
Written by: Chris Lincoln
Site Columns and Site Content Types are a great feature of SharePoint. They’re easy to create/modify and provide granular configuration capabilities. It’s commonly known that the Title Site Column can’t be removed from Site Content Types (or List Content Types, for that matter); it’s attached to the Item Base Content Type, after all.
But did you know that there are many Site Columns that can’t be removed from Site or List Content Types?
But did you know that there are many Site Columns that can’t be removed from Site or List Content Types?
Written by: Chris Lincoln
Do you have a customized SharePoint page that uses the query string variable “ID” to identify a List Item by its ID value? Did SharePoint throw an error that “no item exists at” that location? Are you certain it exists?
If you answered “yes” to each of the above questions, switch your query string variable name from “ID” to something -anything- else.
SharePoint 2010 apparently reserves “ID” for peculiar usage and therefore cannot be used as freely as with SharePoint 2007.
Written by: Chris Lincoln
By default, SharePoint 2007 creates a new column within a List when an attached workflow is started for the first time. The displayed column value is a verbose workflow status (e.g. “In Progress”, “Error Occurred”, etc.). However, if List Items are retrieved from a List View containing such a “workflow column” using the Lists Web Service, the returned values of any workflow columns are not verbose. In fact, they’re the opposite…
Written by: Johnny Bouder
For all of you out there that have not yet been allowed the opportunity to dig into the vastness that is SharePoint 2010 and have become bored with SharePoint 2007, I just might have something new for you to play with. That’s right…PowerShell! My new addiction…
Note that before getting started, you should have a good working knowledge of the SharePoint Object Model.
Step 1: Get started
PowerShell by default comes with Windows Server 2008, however it doesn’t come with Windows Server 2003 and my guess is that if you’re still running SharePoint 2007 you’re probably still running Server 2003. If you are among this group, all you need to do is install the hotfix (KB926139) on one of your web servers. If you’re running Server 2008, you’re ready to go.
Step 2: Get excited!
So without getting too deeply into the nuts and bolts of PowerShell, what you need to know is that it gives you a command line interface, which provides the added ability of leveraging compiled code without actually compiling any of your own code. How could anyone not be excited about that?
And given the richness of the SharePoint object model, you are basically given unlimited potential for managing your SharePoint applications…
Written by: Derek Yale
On Tuesday, April 5th, MetroStar Systems announced our support in the successful development and redesign of the Federal Communications Commission’s (FCC) FCC.gov website into a new digital platform: http://beta.fcc.gov!
Written by: Jorge "El Che" Vasquez
SilverLight is a great presentation display. However, when it works perfectly on ALL Browsers, with exception of Internet Explorer, it become very comical. Background We developed a SilverLight display which uses “WebClient” class to query an RSS feed asynchronously: WebClient proxy = new WebClient(); proxy.OpenReadCompleted += new OpenReadCompletedEventHandler(OnReadCompleted); Once the callback event is triggered by …
Written by: Lee Kohn
If you ever have had the need to create your own pagination for SharePoint 2010 lists/views you will undoubtedly have run into a class called SPListItemCollectionPosition which is supposed to handle going forwards and backwards in the paging. Unfortunately as of this post the documentation on this little gem is non-existent. So after doing some googling and experimentation …
