ClickOnce prerequisite issue


I am using ClickOnce to deploy a WPF application that is built using .NET 3.5 SP1.

When I set up the prerequisites, only .Net Framework 3.5 appears in the prerequisite dialog box and I obviously want to be able to select SP1.

Any idea why this is not appearing?

Who is Participating?
Death259Connect With a Mentor Commented:
In order to specifically target 3.5sp1, there are a few things you can do: 1) make one of the pre-requisites be .net 3.5sp1  2)in the project properties window, under the publish tab, go to Options then Manifests and check "Create desktop shortcut".

The desktop shortcut was a new addition to 3.5sp1 and thus can only be used by computer having .net 3.5sp1
The prerequisites box is autmoatically filled with what your application actually requires -- I'm pretty sure if SP1 isn't there then its simply not something your project requires, so why force the user to get it?
swilson33Author Commented:
My mistake - I've just seen that my app is targetting .Net framework 3.5 - I'm obviously not tapping into the new SP1 features within my WPF app.

So how do you specifically target .net 3.5 SP1?
Below is a list of feature in SP1
.NET Framework version 3.5 Service Pack 1 provides the following new features and improvements:

    * ASP.NET Dynamic Data, which provides a rich scaffolding framework that enables rapid data driven development without writing code, and a new addition to ASP.NET AJAX that provides support for managing browser history (back button support). For more information, see What’s New in ASP.NET and Web Development.

    * Core improvements to the CLR (common language runtime) that include better layout of .NET Framework native images, opting out of strong-name verification for fully trusted assemblies, improved application startup performance, better generated code that improves end-to-end application execution time, and opting managed code to run in ASLR (Address Space Layout Randomization) mode if supported by the operating system. Additionally, managed applications that are opened from network shares have the same behavior as native applications by running with full trust.

    * Performance improvements to WPF (Windows Presentation Foundation), including a faster startup time and improved performance for Bitmap effects. Additional functionality for WPF includes better support for line of business applications, native splash screen support, DirectX pixel shader support, and the new WebBrowser control.

    * ClickOnce application publishers can decide to opt out of signing and hashing as appropriate for their scenarios, developers can programmatically install ClickOnce applications that display a customized branding, and ClickOnce error dialog boxes support links to application-specific support sites on the Web.

    * The Entity Framework is an evolution of the existing suite of ADO.NET data access technologies. The Entity Framework enables developers to program against relational databases in according to application-specific domain models instead of the underlying database models. For more information, see Getting Started with the Entity Framework. The Entity Framework introduces some additional features, including support for new SQL Server 2008 types, default graph serialization of Entities, and the Entity Data Source. This release of the Entity Framework supports the new date and file stream capabilities in SQL Server 2008. The graph serialization work helps developers who want to build Windows Communication Foundation (WCF) services that model full graphs as data contracts. The Entity Data Source provides a traditional data source experience for ASP.NET Web application builders who want to work with the Entity Framework.

    * LINQ to SQL includes new support for the new date and file stream capabilities in SQL Server 2008.

    * The ADO.NET Data Services Framework consists of a combination of patterns and libraries, which enable data to be exposed as a flexible REST (Representational State Transfer)-based data service that can be consumed by Web clients in a corporate network or across the Internet. The ADO.NET Data Services Framework makes data service creation over any data source. A conceptual view model of the underlying storage schema can easily be exposed through rich integration with the ADO.NET Entity Framework. Services created by using the ADO.NET Data Services Framework, and also compatible Windows Live ( services, can be easily accessed from any platform. For client applications that are running on Microsoft platforms, a set of client libraries are provided to make interaction with data services simple. For example, .NET Framework-based clients can use LINQ to query data services and a simple .NET Framework object layer to update data in the service.

    * Windows Communication Foundation now makes the DataContract Serializer easier to use by providing improved interoperability support, enhancing the debugging experience in partial trust scenarios, and extending syndication protocol support for wider usage in Web 2.0 applications.

    * The .NET Framework Data Provider for SQL Server (SqlClient) adds new support for file stream and sparse column capabilities in SQL Server 2008.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.