Feeds:
Posts
Comments

Posts Tagged ‘development’

SharePoint & Office Conference 2010 in Milan

Howdy,

This is a live blog post from the current talk Jan Tielens is giving. I’ll give  you the quick topics.

There exists a basic SL Web Part, that can display any SL application delivered as .xap (and accessible via a URL, of course).

Most important property of it: You can set a .XAP file’s URL.

How it is done:

  1. Upload a .XAP to a document library(Shared Documents)
  2. Copy the URL of the .XAP
  3. Insert the SL Web Part from “Media and Content” area
  4. Paste the URL into the Web Part
  5. Set the Web Part’s width to variable (not fixed), otherwise it’ll issuean error

How to Deploy

1. Virtual File System

  • Add module item (Add –> New Item)
  • Past the .XAP into the module (Elements.xml will now contain a ref to the .XAP)

2. Physical File System

In the 14\TEMPLATE\LAYOUTS folder

  • 15\TEMPLATE\LAYOUTS\ClientBin (default)
  • Advantage: Becomes available right away!

3. Solutions:

  • Add a mapped folder (e.g. above mentioned LAYOUTS) to the solutions
  • Copy .xap into it

Important: For sandboxed solutions, only deployment to VFS is possible.

Client Object Models

Definition: Simple API to add, Retrieve, Update and Manage SP data

DLLs are location in the 14\TEMPLATE\LAYOUTS\ClientBin folder

How to Build Silverlight Web Parts

Create a new project (SL enabled), and put the following code snippets into a User Control.

Add a reference to the Microsoft.SharePoint.Silverlight*.dll files.

Data Binding is done like this in SL:

   1: <DataTemplate>

   2:     <TextBlock Text="{Binding Title}"></TextBox>

   3: </DataTemplate>

Snippet 1: Basic data binding in SL

   1: using (ClientContext ctx = new ClientContext("http://urlToSharePoint"))

   2: {

   3:     items = ctx.Web.Lists.GetByTitle("Videos");

   4:     ctx.Load(items);

   5:     ctx.ExecuteQueryAsync(Success, Fail);

   6: }

Snippet 2: Using the Client Object Model API. Success and Fail are callback methods you have to define. items is a ListItemCollection you’ll have to define in the user control as  a member variable.

As we saw yesterday at an in-depth look of the Client Object, you can also retrieve

Next, marshall the thread from the UI back (in Success/Fail)

   1: this.Dispatcher.BeginInvoke(() =>

   2: {

   3:     //Here we can work with the list items

   4:     foreach(ListItem item in items)

   5:     {

   6:         //Do sth, e.g. add new items

   7:     }

   8: }

Snippet 3: dispatcher invocation

Jan goes one step further and displays the playing of videos by putting a <MediaElement> into the XAML.

Customizable SL Web Parts

The advantage over the Out-of-the-Box web part is that you can add customization value to it:

E.g. adding own properties

BTW: Parameters are passed to SL web parts using the initParams

   1: <param name=’initParamsvalue=’docLib{0}’/>

Snippet 4: Replace {0} with you custom property name, or make it a String.Format!

These can be accessed in Application_Startup method of theSL App like this:

   1: e.initParams("docLib")

Snippet 5: Accessing the initParams
You can also run your SL app outside the browser. You can do this by going to your project’s SL tab and setting the “Run out of the browser” checkbox. This enables your webpart to be downloadable to the client and be executable as a client app!
Keep going, Jan!

Cheers,

Martin

Advertisements

Read Full Post »

Howdy folks,

Here we are back again with an introduction of the new features of the upcoming Visual Studio 2010. Its release has been postponed to the 12th of April, so in the meantime we’ll have to stick to the Beta 2, which is pretty stable already. There are so many improvements that we’ll have to divide it into multiple parts. Let’s dive right in!

1. UI: WPF-Based

The UI is now WPF based, which means a better usability and more extensibility options for us developers. Clearly, introducing VS2010 as a WPF-based application is a big push in the direction of visualization and diagramming. We’ll see later how this can be performed using the new IDE.

The editor, for example, is now WPF-based. Cool, but what does that mean for us? Here are the advantages:

Change font size w/ mouse only, or better: No more Options->Change font size during presentations!

Extension Manager allows easy-to-install-and-use add-ins: Also from online galleries – Single click install and enabling!

Highlighting of related variable/method names (Figure 1)

clip_image002

Figure 1: Highlighting related variable. Note that the highlighter correctly references only the name variable passed as a parameter

You can navigate between the highlighted elements using CTRL + SHIFT and the ARROW keys!

2. Intellisense – Improvements:

Method Matching: When VS2010 brings up the list of available methods (after you typed something), it performs not a simple .StartsWith name comparison, but a .Contains. This leads to the results shown on the next screenshots:

Filtered list is gone: When typing letters, the auto completion list that pops up won’t give you all objects/methods/variables that start with the same letter, but only those who are truly related. Consider Figure 3: We typed IF. In the old version, VS would have brought up not only the items shown in the completion list, but possibly many many more, all starting with I (but not containing or continuing with F). Now the IntelliSense search is narrowed, which makes it a lot easier for the developer to select the correct entry.

clip_image004

Figure 2: Highlighting the related object/variable/method.

Case sensitivity: Another nice feature highlighted in figure 2 is the Pascal-Case typing of the capital letters IF, which brings correctly up our method, since its signature contains both I and F as of the method name. Try typing If (f is lowercase), and you won’t find the IsFasterThan method in the auto completion list anymore.

3. References dialog improvements

Remember the Add References dialog in figure 3?

clip_image006

Figure 3: Add references underwent some perception changes.

First of all, Microsoft realized that most people are using it to reference other projects, so they brought up the Projects tab by default. But that’s not all: We all LOVED to wait 30 seconds for the list of .NET or COM objects to appear, right? Because of that, while we are browsing by default the projects, VS2010 is asynchronously loading the available assemblies already. Saves time and nerves.

4. Search and Navigation

Let’s press CTRL + , anywhere in the editor. The window Navigate To will appear, providing us a very powerful search across the entire solution. The search results are updated as we type. From here, we can navigate directly to the found item. Figure 4 shows the dialog.

clip_image008

Figure 4: The Navigate To dialog is a powerful search and navigation mechanism, providing also essential information about the found items. Big improvement over the VS2008 style’s CTRL+SHIFT+F (and subsequent find results crawling without navigation to the desired item)!

5. Call Hierarchy

Remember the Find All References option in the editor’s context menu? It provided us information about where a method/variable has been used. Tell you what. We have a much more powerful way of doing this now: The Call Hierarchy option (Figure 5).

clip_image010

Figure 5: Context menu for the IsFasterThan method, highlighting the new View Call Hierarchy option.

This is the result: A list of all callers (“Calls To”) and callees (“Calls From”) of IsFasterThan (Figure 6). Every caller/callee can be expanded into its own callers/callees. As of figure 6, e.g. Main. This is a really expressive feature which outperforms Find All References by far. However, a possible drawback might be that you could expand the list to infinity by alternating the caller/callee relationship. Figure 6 shows the resulting

image

Figure 6: The View Call Hierarchy window, showing callers/callees of IsFasterThan.

6. Project dialog with search and .NET version selection

Figure 7 shows the improved New Project dialog.

clip_image012

Figure 7: The NewProject dialog. Please note the search field in the right upper corner and the .NET framework dropdown list (center), where now also version 4 of the .NET framework is available.

7. Code Snippets

The code snippets are accessible via the Tools menu, or by pressing the shortcut CTRL + K, CTRL + B

Additional snippets are now available also for HTML, JavaScript and SQL. In sub-categories you can find the different snippets already provided by VS2010. Moreover, you can add your own snippets (as we already know from previous VS versions), as well as remove and import snippets. Figure 8 shows the Code Snippets dialog.

clip_image002[1]

Figure 8: The Code Snippets dialog, showing the newly available languages, as well as subcategories in the Code Snippets Manager.

8. Environment settings: Code Optimized

One more newly available feature is a new default environment setting (remember you had to choose which default settings you wanted to use when starting VS2010 for the first time?). There is one newly available feature which will simply allow you to reduce your viewport to only the code when developing (hence removing the designer). If you have already chosen your first-time-startup environment settings: Don’t worry! The next screenshot explain how you can access the new Web Development (Code Optimized) default environment setting. First, choose Tools –> Import and Export Settings.

image

Figure 9: Import and Export Settings wizard. Choose Reset all settings here. Then you will be prompted whether or not you want to save your current settings. Choose as you wish there. Then proceed.

image

Figure 10: Default environment settings. Note the Web Development (Code Optimized) option, which is new to VS2010. Choose it and VS will immediately switch to those settings, removing e.g. the designer buttons and providing you with a much more lightweight code editor window. Very handy for developers who want to only focus on the code.

9. Conclusion

So I’d say this is about it for this time. Of course there are a lot more features which need to be covered.

The next lessons will deal with creating customized startup pages for VS2010, and introduce the new language features and tools of Visual Studio 2010.

In the meantime, enjoy exploring VS’ new capabilities and features, and hang on till the next time!

Best regards,

Martin

Read Full Post »