.Net Support

As we near the end of the SDK documentation there are only a few more things to cover. While most of remaining functions fall into a specific category a few don't, so I' ll be spreading those that don't between parts eight and nine (the last article). The main focus for this article is layer rights (or permissions), layer priority and processes (namely ignoring them and running one from an existing layer).

A common problem people have with SVS is trying to add new files to a layer. It's very common for someone to try to just add, via Windows Explorer, to the virtualized path. Experienced SVS users know this won't work since the virtualized path is just that, virtual, and while the file will get moved it won't get into the layer itself. So, when you export, that moved file won't be in the package.

You can use the ASDK to programmatically generate incidents but you are limited to using the subject and body fields when creating them. You can then use the ASDK to modify fields one by one, which means if you are changing 5+ fields the workers will have to scroll halfway down the page to view the body of an incident.

OnEvents are one of my favorite features of SVS, they allow you to really expand what you can do with a layer. The currently available tools, however, (SVSCmd, SVSAdmin and even Wise Studio) either don't offer any way to manage them or offer a very poor system for doing so. Thankfully, managing OnEvents with the SDK is very easy.

Being able to capture applications or updates in a layer is the Holy Grail of the SVS SDK and, well, the reason people use SVS. Surprisingly, creating and capturing layers is one of the simplest things to do with the SDK, especially when compared to Export and Import. With the information presented in this article you should easily be able to implement these SVS features into any tool you're making.

By now if you've been following along with my article series you should be able to initialize SVS, perform common actions and Import and Export, so what next? A common task in SVS is to get a layer name from a GUID or vice-versa, which is where Layer Attributes come into play. But it's not just getting GUIDs, you can do a lot more with SVS Attributes such as the location of the redirect paths or if a layer is active or not.

I will be providing a class, named FLS2 that you can download and use as well as articles on how to use the class. At first there won't be many methods in FSL2 because I'll only add them as I complete the documentation. There's also a lot I haven't used or marshaled in as of this writing. To make things easy and simple every time there's a new article posted and the class is updated I'll put all notes here -- in this book.

In Part Two of my SVS SDK series I covered common methods such as activate and delete. Please review those articles before reading this one because I won't cover anything mentioned in Part One or Part Two here. Hint: the methods covered in Part Three won't work without what was covered in Part One.

In part one of my SVS SDK series I covered why I'm creating these articles and how to use the SDK to properly initialize SVS. Please read over it before reading this article because I won't cover anything mentioned in Part One here and many of the methods covered in Part Two won't work without what was mentioned in Part One.

PowerShell is the new powerful scripting language created by Microsoft. You can install it to Windows XP and above and it is included in Windows Server 2008.

Here is how to run a PowerShell Script through Deployment Server.