Windows

Sponsored and paid for by CipherPoint. New Software Expands Addressable Market and Helps Organizations Identify Security and Compliance Risks CipherPoint™ announces Version 1.9 of the company's CipherPointSP software, bringing the company's transparent encryption technology to users of SharePoint 2013 and to file server environments. In addition, the company released the CipherPointCS content scanner. The new CipherPoint software capabilities include: File Server Encryption: A new agent, CipherPointFS™, is available providing transparent encryption for unstructured content in file servers. This new capability builds on CipherPoint's unique offerings for encryption and key management, bringing this functionality to users of file servers. ;Support for SharePoint 2013: CipherPointSP Enterprise now includes support for SharePoint 2013 environments, in addition to the previously supported SharePoint 2007/2010. ;CipherPointCS™ content scanner: CipherPoint has released an improved version of our content scanner, CipherPointCS. The new release provides improved accuracy with respect to false positives. CipherPointCS allows SharePoint and IT security administrators to easily scan SharePoint repositories, and find sensitive and compliance regulated information such as Social Security Numbers and Credit Card data.  This collection of new capabilities greatly expands the coverage that CipherPoint provides for protecting unstructured data. CipherPoint can now encrypt and control access to data in SharePoint 2007, 2010, and 2013 sites, and in file servers. CipherPoint can also scan and find sensitive and compliance-regulated data in these environments. All of these products are available now. Contact CipherPoint for pricing. "Broadening support for unstructured data encryption to include file servers and SharePoint 2013 makes a lot of sense for Logicalis and our customers" said Patrick Simmons, Consulting Director at Logicalis. "Having a best of breed transparent encryption capability for these new platforms, plus having a content scanning product, will help us to find and secure sensitive and regulated data in customer environments." "CipherPoint's customers have asked us to extend our platform coverage to include SharePoint 2013 and file servers" said Mike Fleck, CipherPoint CEO. "In addition, we've improved our content scanner technology to include the feedback we received during the public Beta program. The combination of releases expands the ability of our customers to quickly and easily identify sensitive and regulated content in file sharing and collaboration environments like SharePoint and file servers." For more information on CipherPoint's transparent encryption solutions, please visit: https://www.cipherpoint.com/data-security/ About CipherPoint Software, Inc. CipherPoint secures sensitive and regulated content in web-based application environments including premise-based collaboration platforms such as Microsoft SharePoint, cloud, and other web-based applications.  CipherPoint's transparent data encryption technology secures content and data from the web tier, affording the highest level of threat protection to sensitive and regulated content. CipherPoint's products are easy to deploy and manage, secure, and scalable to meet the needs of large enterprises. Headquartered in Denver, Colorado, CipherPoint was founded by IT security experts with deep experience in building successful security technology companies. Customers in healthcare, financial services, manufacturing, government, and other industries, in Europe, North America, and Asia rely on CipherPoint to protect access to sensitive or regulated information in file sharing and collaboration environments like SharePoint and file servers." CipherPoint Software, Inc., 1730 Blake St., Suite 400, Denver, CO 80202 1.888.657.5355 info@cipherpoint.com. Sponsored and paid for by CipherPoint.

I’m going to be on the Blog Talk Radio Collaboration Tech Talk on June 6 visit the show to get the times, and call in detail. “Our guest will be Joel Oleson, a social media strategist, Intranets guru and SharePoint evangelist.  He is also Managing Director at Salient6, and authors a blog as SharePoint Joel.  In this interview, Joel will talk about the recent release of SharePoint 2013, and what developers, end users and managers can expect. Topics will address most interesting SharePoint 2013 features, including new developer tools, and exciting social media and mobile functionality. We will also explore prospects for public and private sector adoption of this latest version of SharePoint. Joining us for Q&A will be Mack Sigman, SharePoint Architect and Practice Leader atCSC, and President of the Federal SharePoint Users Group (FEDSPUG) in Washington D.C. Gary Vaughan, Senior IT and Knowledge Management Advisor with Glotech at the State Department, will be the show host. Gary also provides independent SharePoint consulting in program and project management, user adoption and requirements in the D.C. area.  Notes and links discussed during this program will later be published on Gary’s blog, “Collaboration Times.””

I dreamed that one of my friends had made the U.S. cycling team. (Perhaps because everybody else got busted for doping.) Even more implausibly, I also made the team. To celebrate, he challenged me to a short race. The path ran along a river, in which a medium-sized boat was setting sail. Our bicycles somehow could fly (which we considered perfectly normal) and we were flying over the boat, just about keeping pace with it. The boat reversed direction many times, and we reversed along with it. At one of the reversals, I thought, "I could take a shortcut if I kept going straight," but I must've lost even/odd count because I flew off the boat... heading back to the starting line. Bonus weirdness: For some reason, we were in Sweden, and the race commentator saw a school labeled Gymnasium and made some remark about repurposing buildings left over from the Olympics.

Today's Little Program takes a fully-qualified file name from the command line and puts that file onto the clipboard. Once there, you can paste it into an Explorer window, or into an email message, or a word processing document, or anybody else who understands shell data objects. #include #include #include #include class COleInitialize { public: COleInitialize() : m_hr(OleInitialize(NULL)) { } ~COleInitialize() { if (SUCCEEDED(m_hr)) OleUninitialize(); } operator HRESULT() const { return m_hr; } HRESULT m_hr; }; // GetUIObjectOfFile incorporated by reference int __cdecl wmain(int argc, PWSTR argv[]) { COleInitialize init; CComPtr spdto; if (SUCCEEDED(init) && argc == 2 && SUCCEEDED(GetUIObjectOfFile(nullptr, argv[1], IID_PPV_ARGS(&spdto))) && SUCCEEDED(OleSetClipboard(spdto)) && SUCCEEDED(OleFlushClipboard())) { // success } return 0; } The COle­Initialize class is just the OLE counterpart to the CCo­Initialize class we saw some time ago. All the program does is take the file name on the command line, asks the shell for the corresponding data object, then puts that object onto the clipboard, erasing what was there before. Once the data is on the clipboard, our job is done so we exit. No, wait! If you exit while your application has data on the clipboard, that clipboard data may be lost. The documentation for Ole­Set­Clipboard notes: If you need to leave the data on the clipboard after your application is closed, you should call Ole­Flush­Clipboard rather than calling Ole­Set­Clipboard with a NULL parameter value. Therefore, we stick in a call to Ole­Flush­Clipboard before exiting. This forces any delay-rendered content to be rendered immediately, because we ain't gonna be around to delay-render it no more. Note that the file on the command line must be fully-qualified, because we pass it straight to Get­UI­Object­Of­File, which expects a fully-qualified path. Fixing the program to allow relative paths (and to actually print error messages and stuff) is left as an exercise, because Little Programs don't deal with annoying details like error checking and reporting.

"Sitting is the smoking of our generation." -

There is a big problem in the RavenDB build process. To be rather more exact, there is a… long problem in the RavenDB build process. As you can imagine, when the build process run for that long, it doesn’t' get run too often. We already had several runs of “let us optimize the build”. But… the actual reason for the tests taking this long is a bit sneaky. To save you from having to do the math, this means an average of 1.15 seconds per test. In most tests, we actually have to create a RavenDB instance. That doesn’t take too long, but it does take some time. And we have a lot of tests that uses the network, because we need to test how RavenDB works on the wire. From that perspective, it means that we don’t seem to have any real options. Even if we cut the average cost of running the tests by half, it would still be a 30 minutes build process. Instead, we are going to create a layered approach. We are going to freeze all of our existing tests, move them to an Integration Tests project. We will create a small suite of tests that cover just core stuff with RavenDB, and use that. Over time, we will be adding tests to the new test project. When that becomes too slow, we will have another migration. What about the integration tests? Well, those will be run solely by our build server, and we will setup things so we can automatically test when running from our own forks, not the main code line.

Scenario - you have an ID of a site column (SPField belonging to SPWeb)and you want to find out if there is a field by that ID in the collection. Problem: if you try something like: web.Fields[fieldID] == null The result is an exception if the field doesnt exist. What a shame. So you choice is to put a try-catch around that code to check for the exception. That does not make for pretty code though, so what I do is: if (!web.Fields.SchemaXml.Contains(fieldID.ToString())) By checking the schemaXml of the fields object, we check if the field ID exists using a simple string comparison.

Body: In tonight's Netcast we talk about some security issues I had with SharePoint last week and how to successfully update the Workflow Manager. Then we dive into a couple of lively discussions. First we cover whether you should install the 32 bit or 64 bit version of Office 2013. After we lay that discussion to rest then we discuss the pros and cons of using SharePoint groups or Active Directory groups when assigning permissions in SharePoint. Then I promote the bejeezus out of my new book. MP3 File WMV File iPod File YouTube (Subscribe) Running Time: 43:22 Links: Account permissions and security settings in SharePoint 2013 Update Workflow in SharePoint Server 2013 Choose 32-bit or 64-bit Office 2013 Use SharePoint groups or AD groups? SharePoint 2013 Building Business Solutions UStream Premium Membership (no commercials during the live stream) SharePoint 2013 Professional Administration TechEd North America TechEd Europe Brought to you by Rackspace ShortURL: http://www.toddklindt.com/Netcast156 Category: Netcast Published: 5/19/2013 8:50 PM

This is an alternative for "Dynamically generate a LINQ query with a custom property"....Did you know that DotNetSlackers also publishes .net articles written by top known .net Authors? We already have over 80 articles in several categories including Silverlight. Take a look: here.

Abstract of my Pluralsight CourseBuilding a Successful BlogModule – Getting Started with Blogging. Thinking about starting a blog? Confused about the entire idea of blogging? I have created a course on Pluralsight relating to this very issue. Lets start with the easy questions: what is the difference between a blog and a website? Websites are […]...Did you know that DotNetSlackers also publishes .net articles written by top known .net Authors? We already have over 80 articles in several categories including Silverlight. Take a look: here.