This is what it is when bing meets tweets = bingtweets.com
Just search anything on the “Search Bing & Twitter”, and you can straight away click “Tweet this” and post it on your twitter.
This is what it is when bing meets tweets = bingtweets.com
Just search anything on the “Search Bing & Twitter”, and you can straight away click “Tweet this” and post it on your twitter.
Came across this article, which is quite interesting and thinking to blog about it. The articles talks about the 10 mistakes done by most of the company that likely to expose your organization to security vulnerabilities. You might find it sounds stupid and unlikely you will do that. But, the more you take it easy, there more you are likely to fall into one of the mistakes. You might want to incorporate these mistakes into your network administration checklist:
1. Not changing the default passwords on all network devices
2. Sharing a password across multiple network devices
3. Failing to find SQL coding errors.
4. Misconfiguring your access control lists
5. Allowing nonsecure remote access and management software
6. Failing to test noncritical applications for basic vulnerabilities
7. Not adequately protecting your servers from malware.
8. Failing to configure your routers to prohibit unwanted outbound traffic.
9. Not knowing where credit card or other critical customer data is stored.
10. Not following the Payment Card Industry Data Security Standards.
For more details, please visit this article.
Tomorrow, July 7th, 10AM PT, 1PM ET – there is a broadcasting the Michael Jackson memorial, live in HD from the Staples Center in Los Angeles using IIS Smooth Streaming and Silverlight to the world. As you can imagine this has come together fast and we need to get the word out so please tweet, blog, facebook, friendfeed, dig, reddit, anywhere and anything you can do to get the word out starting NOW!
http://inmusic.ca/news_and_features/Michael_Jackson is the link to the page where the embedded player experience and is the URL you should share and use.
Visual Studio 2008 is a 32-bit application and when installed on a 64-bit Windows operating system will run under WOW64. When installing VS 2008 32-bit version , the Visual Studio will install the 32-bit version 2.0 CLR on an x86 machine, and both the 32-bit and appropriate 64-bit version 2.0 CLR on a 64-bit Windows machine.
Here is the system requirement for Visual Studio 2008:
Software requirements:
32 bit OS: Windows® XP Professional with Service Pack 2 installed, Windows Server 2003, or Windows Vista
64 bit OS: Microsoft Windows Server® 2003 with SP1, Standard x64 Edition (WOW)
- Microsoft Windows Server 2003 with SP1, Enterprise x64 Edition (WOW)
- Microsoft Windows Server 2003 with SP1, Datacenter x64 Edition (WOW)
- Microsoft Windows Server 2003 R2, Standard x64 Edition (WOW)
- Microsoft Windows Server 2003 R2, Enterprise x64 Edition (WOW)
- Microsoft Windows Server 2003 R2, Datacenter x64 Edition (WOW)
- Microsoft Windows XP Professional x64 Edition (WOW)
- Windows Vista
For more information, see the links:
1. http://msdn.microsoft.com/en-us/library/ms241064.aspx
2. http://www.microsoft.com/visualstudio/en-us/products/professional/default.mspx
3. http://msdn.microsoft.com/en-us/library/ms246588.aspx
VSTS 2010 beta 1 is available for download!!! Go to http://msdn.microsoft.com/en-us/teamsystem/dd582936.aspx A lot of new cool features and general improvement in the UI. From customers request, Architect edition supports UML with great visualization. TFS now has visualize source heirachy and allows you to drag and drop changeset from braches.
Check it out!!
For those who are getting error when open Excel documents stored on the TFS.
“TF84037: There was a problem initializing the Microsoft Excel Team Foundation Addin. Re-installing the Team Foundation Client may be required.”
The reason is because the Office .Net programmability support is not installed. You need to modify your installed version of Office and install this option.
1. In Add/Remove programs, locate your Office application and select it.
2. Click on the ‘Change’ button
3. Select ‘Add or Remove features’ and click ‘next’
4. Select ‘Choose advanced customization of applications’ and click ‘next’
5. In the tree view, expand ‘Microsoft Office Excel’ and make sure the .NET Programmability Support option is set to ‘run from my computer’.
6. Click ‘update’
On 13th February 2009, usergroups from SPAN, SCUG, SPUG and myVSTS had organized a community day in Microsoft’s office. The objectives to have this community day are:
1. To have a technology update session for the community members on various technologies, including System Center, Microsoft SQL Server, Microsoft SharePoint and Visual Studio Team System.
2. Enable the community members from different user groups to get to know each other in the networking session.
In total, we had 4 tracks during the breakout sessions: System Center, SQL Server, Visual Studio Team System and SharePoint Server.

Attendees were listening to the keynote session.

Usergroup members were listening to the SQL session in one of the tracks.
Thanks for the speakers: Sin Min, CK Phua, KB Lim, Ervin Loh, Wei Kheng and Patrick. And thanks to the supporters who helped out in the events, Walter, Raymond, Keong Yee, Moy, Yu Tsing, Zhariff and Leo.
Of course, there is food for the attendees. This round, we were getting PIzzas…Yes, is pizza again. Simple and easy to handle for the organizers
For those using Team Foundation Server 2005 or 2008, you might still have .NET 1.1 applications that need to be maintained in your organization. The good thing is you can still use MSSCCI provider for TFS 2005 or MSSCCI provider for TFS 2008 installed on your Visual Studio 2003 machines and check in your .NET 1.1 applications to the TFS. At least, you have the TFS as a single repository for all the source code.
How about the TeamBuild in TFS, can that apply to .NET 1.1 applications? If you are using the TeamBuild to build your source code in TFS, you might be wondering, wouldn’t it be good if I can use the TeamBuild to build my .NET 1.1 applications? However, the answer is “NO”!! Team Build doesn’t support .NET 1.1 applications by default.
There are few options you can do:
1. Update your project to Visual Studio 2005 and above projects. The MSBuild Extras – Toolkit for .NET 1.1 (MSBee) allows .NET 1.1 builds but requires that your projects and solutions be upgraded to Visual Studio 2005.
2. If you cannot upgrade the .NET 1.1 applications to Visual Studio
2005 projects and solutions, you can use a custom post-build step to compile the .NET 1.1 applications.
See Nagaraju’s blog entry at http://blogs.msdn.com/nagarajp/archive/2005/10/26/485368.aspx give you a heads up on how to enable TeamBuild for .NET 1.1 applications.
The Layered Architecture Sample is updated and you can download from codeplex now: LayerSample January 2009 Release (now comes with ADO.NET EF).
For more info, visit Serena’s blog post.