clientdependency Releases Rss Feed

Updated Release: v1.6.0 (Apr 17, 2013)

Shandem — Thu, 25 Apr 2013 23:58:54 GMT

This release brings you many bug fixes and some new features

Install via Nuget:

PM> Install-Package ClientDependency
PM> Install-Package ClientDependency-Mvc

This will be the last release distributed on CodePlex. The project has now moved to GitHub: https://github.com/Shandem/ClientDependency

And even more good news is that the documentation on GitHub is up to date and far more straight forward!

Supported versions

ClientDependency.Core 1.6 now requires .Net Framework 4.0
ClientDependency.Core.Mvc 1.6 now requires ASP.Net MVC 4.

New features

Bugs fixed

Fix for CssMedia property (13214)
Fix for RenderJsHere with no dependencies (13215)
RenderJsHere, RenderCssHere to return IHtmlString (13216)
CDF attribute css media issue (13207)
Base64 Encoded Images break fix (13203)
css @import directive fix (13204)
Performance fixes for ensuring no duplicates
natural ordering fix (13217)
JSMin issue - re-ported latest c codebase to c# (13197)
Fixes forced provideres with MVC

Breaking changes

Ensure you read the breaking changes for the previous release if you are upgrading from a release older than 1.5.1

The only breaking change for this release is that the Webforms PlaceholderProvider is now the default so if you are using the minimal CDF config then please note that the PlaceholderProvider is the default. You can easily change the default back to the LoaderControlProvider by changing the config.

Upgrading

Just copy over the DLLs. Ensure to read the upgrade instructions for the previous release if you are upgrading from a version older than 1.5.1.

Released: v1.6.0 (Apr 17, 2013)

Thu, 25 Apr 2013 23:58:54 GMT

This release brings you many bug fixes and some new features

Install via Nuget:

Supported versions

ClientDependency.Core 1.6 now requires .Net Framework 4.0
ClientDependency.Core.Mvc 1.6 now requires ASP.Net MVC 4.

New features

Bugs fixed

Fix for CssMedia property (13214)
Fix for RenderJsHere with no dependencies (13215)
RenderJsHere, RenderCssHere to return IHtmlString (13216)
CDF attribute css media issue (13207)
Base64 Encoded Images break fix (13203)
css @import directive fix (13204)
Performance fixes for ensuring no duplicates
natural ordering fix (13217)
JSMin issue - re-ported latest c codebase to c# (13197)
Fixes forced provideres with MVC

Breaking changes

Upgrading

Just copy over the DLLs. Ensure to read the upgrade instructions for the previous release if you are upgrading from a version older than 1.5.1.

Updated Release: v1.6.0 (Apr 17, 2013)

Shandem — Wed, 17 Apr 2013 18:50:35 GMT

This release brings you many bug fixes and some new features

Install via Nuget:

New features

Bugs fixed

Fix for CssMedia property (13214)
Fix for RenderJsHere with no dependencies (13215)
RenderJsHere, RenderCssHere to return IHtmlString (13216)
CDF attribute css media issue (13207)
Base64 Encoded Images break fix (13203)
css @import directive fix (13204)
Performance fixes for ensuring no duplicates
natural ordering fix (13217)
JSMin issue - re-ported latest c codebase to c# (13197)
Fixes forced provideres with MVC

Breaking changes

Upgrading

Just copy over the DLLs. Ensure to read the upgrade instructions for the previous release if you are upgrading from a version older than 1.5.1.

Released: v1.6.0 (Apr 17, 2013)

Wed, 17 Apr 2013 18:50:35 GMT

This release brings you many bug fixes and some new features

Install via Nuget:

New features

Bugs fixed

Fix for CssMedia property (13214)
Fix for RenderJsHere with no dependencies (13215)
RenderJsHere, RenderCssHere to return IHtmlString (13216)
CDF attribute css media issue (13207)
Base64 Encoded Images break fix (13203)
css @import directive fix (13204)
Performance fixes for ensuring no duplicates
natural ordering fix (13217)
JSMin issue - re-ported latest c codebase to c# (13197)
Fixes forced provideres with MVC

Breaking changes

Upgrading

Just copy over the DLLs. Ensure to read the upgrade instructions for the previous release if you are upgrading from a version older than 1.5.1.

Updated Release: v1.5.1 (Jun 01, 2012)

Shandem — Mon, 04 Jun 2012 15:15:49 GMT

This release brings you many bug fixes and some new features

IMPORTANT
If you were of the very few people who have downloaded and installed 1.5.0.x then you need to upgrade to this version (1.5.1) since the 1.5.0.x assemblies were signed but this will break projects that rely on the CDF framework already so this 1.5.1 release has removed the assembly signing.

Install via Nuget:

Install-Package ClientDependency
Install-Package ClientDependency-Mvc

New features

New PlaceHolderProvider for webforms which will now let you specify exactly where the CSS and JS is rendered, so you can now separate them
Better API support for runtime changes & registration
Allows for custom formatting of composite file URLs
- new config option: pathUrlFormat="{dependencyId}/{version}/{type}" to have full control of how the composite paths are created

Bugs fixed

CSS @import directives working (8705,13189)
CSS minify issue (13184)
Machine Name & med trust compatibility (13191)
ResponseFilterStream issue (13188)
Multiple CSS media types (12054)
Ability to specify different render locations of JS/CSS in webforms (12263)
FIPS compliance (13194)
Base64 decoding (13199)
Path length calculations fixed
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

The same breaking changes from v1.4 regarding RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile methods are the same
The BaseCompositeFileProcessingProvider.GetCompositeFileUrl method signature has changed and a 'version' parameter has been added
The v1.4 breaking changes regarding config files changes are no longer breaking changes, legacy config will still work however it is recommended to upgrade your config:
- "fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
- "defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
- "providers" element under "compositeFiles" element renamed to "fileProcessingProviders"

Upgrading Umbraco pre v4.8 release

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page

Released: v1.5.1 (Jun 01, 2012)

Mon, 04 Jun 2012 15:15:49 GMT

Install via Nuget:

Install-Package ClientDependency
Install-Package ClientDependency-Mvc

New features

New PlaceHolderProvider for webforms which will now let you specify exactly where the CSS and JS is rendered, so you can now separate them
Better API support for runtime changes & registration
Allows for custom formatting of composite file URLs
- new config option: pathUrlFormat="{dependencyId}/{version}/{type}" to have full control of how the composite paths are created

Bugs fixed

CSS @import directives working (8705,13189)
CSS minify issue (13184)
Machine Name & med trust compatibility (13191)
ResponseFilterStream issue (13188)
Multiple CSS media types (12054)
Ability to specify different render locations of JS/CSS in webforms (12263)
FIPS compliance (13194)
Base64 decoding (13199)
Path length calculations fixed
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

The same breaking changes from v1.4 regarding RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile methods are the same
The BaseCompositeFileProcessingProvider.GetCompositeFileUrl method signature has changed and a 'version' parameter has been added
The v1.4 breaking changes regarding config files changes are no longer breaking changes, legacy config will still work however it is recommended to upgrade your config:
- "fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
- "defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
- "providers" element under "compositeFiles" element renamed to "fileProcessingProviders"

Upgrading Umbraco pre v4.8 release

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page

Updated Release: v1.5.1 (Jun 01, 2012)

Shandem — Mon, 04 Jun 2012 15:07:04 GMT

Install via Nuget:

Install-Package ClientDependency
Install-Package ClientDependency-Mvc

New features

New PlaceHolderProvider for webforms which will now let you specify exactly where the CSS and JS is rendered, so you can now separate them
Better API support for runtime changes & registration
Allows for custom formatting of composite file URLs
- new config option: pathUrlFormat="{dependencyId}/{version}/{type}" to have full control of how the composite paths are created

Bugs fixed

CSS @import directives working (8705,13189)
CSS minify issue (13184)
Machine Name & med trust compatibility (13191)
ResponseFilterStream issue (13188)
Multiple CSS media types (12054)
Ability to specify different render locations of JS/CSS in webforms (12263)
FIPS compliance (13194)
Base64 decoding (13199)
Path length calculations fixed
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

The same breaking changes from v1.4 regarding RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile methods are the same
The BaseCompositeFileProcessingProvider.GetCompositeFileUrl method signature has changed and a 'version' parameter has been added
The v1.4 breaking changes regarding config files changes are no longer breaking changes, legacy config will still work however it is recommended to upgrade your config:
- "fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
- "defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
- "providers" element under "compositeFiles" element renamed to "fileProcessingProviders"

Upgrading Umbraco pre v4.8 release

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page

Updated Release: v1.5.1 (Jun 01, 2012)

Shandem — Mon, 04 Jun 2012 15:04:05 GMT

This release brings you many bug fixes and some new features

Install via Nuget:

Install-Package ClientDependency
Install-Package ClientDependency-Mvc

New features

New PlaceHolderProvider for webforms which will now let you specify exactly where the CSS and JS is rendered, so you can now separate them
Better API support for runtime changes & registration
Allows for custom formatting of composite file URLs
- new config option: pathUrlFormat="{dependencyId}/{version}/{type}" to have full control of how the composite paths are created
Assemblies now signed with strong names

Bugs fixed

CSS @import directives working (8705,13189)
CSS minify issue (13184)
Machine Name & med trust compatibility (13191)
ResponseFilterStream issue (13188)
Multiple CSS media types (12054)
Ability to specify different render locations of JS/CSS in webforms (12263)
FIPS compliance (13194)
Base64 decoding (13199)
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

The same breaking changes from v1.4 regarding RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile methods are the same
The BaseCompositeFileProcessingProvider.GetCompositeFileUrl method signature has changed and a 'version' parameter has been added
The v1.4 breaking changes regarding config files changes are no longer breaking changes, legacy config will still work however it is recommended to upgrade your config:
- "fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
- "defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
- "providers" element under "compositeFiles" element renamed to "fileProcessingProviders"

Upgrading Umbraco pre v4.8 release

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page

Updated Release: v1.5.1.0 (Jun 01, 2012)

Shandem — Mon, 04 Jun 2012 15:03:50 GMT

This release brings you many bug fixes and some new features

Install via Nuget:

Install-Package ClientDependency
Install-Package ClientDependency-Mvc

New features

New PlaceHolderProvider for webforms which will now let you specify exactly where the CSS and JS is rendered, so you can now separate them
Better API support for runtime changes & registration
Allows for custom formatting of composite file URLs
- new config option: pathUrlFormat="{dependencyId}/{version}/{type}" to have full control of how the composite paths are created
Assemblies now signed with strong names

Bugs fixed

CSS @import directives working (8705,13189)
CSS minify issue (13184)
Machine Name & med trust compatibility (13191)
ResponseFilterStream issue (13188)
Multiple CSS media types (12054)
Ability to specify different render locations of JS/CSS in webforms (12263)
FIPS compliance (13194)
Base64 decoding (13199)
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

The same breaking changes from v1.4 regarding RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile methods are the same
The BaseCompositeFileProcessingProvider.GetCompositeFileUrl method signature has changed and a 'version' parameter has been added
The v1.4 breaking changes regarding config files changes are no longer breaking changes, legacy config will still work however it is recommended to upgrade your config:
- "fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
- "defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
- "providers" element under "compositeFiles" element renamed to "fileProcessingProviders"

Upgrading Umbraco pre v4.8 release

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page

Updated Release: v1.4 (Aug 24, 2011)

Shandem — Mon, 04 Jun 2012 12:06:53 GMT

This release brings you many new features and bug fixes

Nuget packages:

New features

Multiple URL types (each has it's own benefits, for full details see documentation: Composite Url Types)
- mapped id (nice urls)
  - This is now the default. It works by creating a map of the required dependencies on the server before rendering out the html request. The map creates a key which acts as a reference to all of the required dependencies
  - Example: /DependencyHandler.axd/a81e571a8b49102634ad102bc5f1ef40/58/js
- base64 with query strings
  - Example: /DependencyHandler.axd?s=L0Nzcy9DdXN0b21Db250cm9sLmNzczsvQ3NzL0Nvbn RlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7&t=Css&cdv=58
- base64 with paths
  - Example: /DependencyHandler.axd/L0Nzcy9DdXN0b21Db250cm9sLmN zczsvQ3NzL0NvbnRlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7/58/css
Dependency grouping
- We now supporting specifying a group number for dependencies. This is very useful to ensure that client side caching is working at its optimum for for common dependencies that exist between pages.
External/CDN dependencies
- You can use CDF to include external or CDN dependencies such as getting jQuery from the Microsoft of Google CDN. Even though this dependency has been registered with CDF, it will make sure that it's rendered in your html markup in the correct order with regards to all of your other dependencies with a separate script/link tag resolving to the external path
Html Attributes
- Now supporting MVC style HTML attributes with new { .. } object syntax so you can specify any html attributes for any dependency (i.e media="print")

Bugs fixed

Server.Transfer issue (13172
ETag generation issue (13171)
ETag formatting issues (13182, 13183)
Dependency groups issue (13169)
CSS Min (13181)
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

"fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
"defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
"providers" element under "compositeFiles" element renamed to "fileProcessingProviders"
Breaking provider changes: With the new Html attribute feature, the provider method signatures: RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile have changed.

Upgrading Umbraco

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page

Released: v1.4 (Aug 24, 2011)

Mon, 04 Jun 2012 12:06:53 GMT

This release brings you many new features and bug fixes

Nuget packages:

New features

Multiple URL types (each has it's own benefits, for full details see documentation: Composite Url Types)
- mapped id (nice urls)
  - This is now the default. It works by creating a map of the required dependencies on the server before rendering out the html request. The map creates a key which acts as a reference to all of the required dependencies
  - Example: /DependencyHandler.axd/a81e571a8b49102634ad102bc5f1ef40/58/js
- base64 with query strings
  - Example: /DependencyHandler.axd?s=L0Nzcy9DdXN0b21Db250cm9sLmNzczsvQ3NzL0Nvbn RlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7&t=Css&cdv=58
- base64 with paths
  - Example: /DependencyHandler.axd/L0Nzcy9DdXN0b21Db250cm9sLmN zczsvQ3NzL0NvbnRlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7/58/css
Dependency grouping
- We now supporting specifying a group number for dependencies. This is very useful to ensure that client side caching is working at its optimum for for common dependencies that exist between pages.
External/CDN dependencies
- You can use CDF to include external or CDN dependencies such as getting jQuery from the Microsoft of Google CDN. Even though this dependency has been registered with CDF, it will make sure that it's rendered in your html markup in the correct order with regards to all of your other dependencies with a separate script/link tag resolving to the external path
Html Attributes
- Now supporting MVC style HTML attributes with new { .. } object syntax so you can specify any html attributes for any dependency (i.e media="print")

Bugs fixed

Server.Transfer issue (13172
ETag generation issue (13171)
ETag formatting issues (13182, 13183)
Dependency groups issue (13169)
CSS Min (13181)
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

"fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
"defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
"providers" element under "compositeFiles" element renamed to "fileProcessingProviders"
Breaking provider changes: With the new Html attribute feature, the provider method signatures: RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile have changed.

Upgrading Umbraco

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page

Created Release: v1.5 (Jun 01, 2012)

Shandem — Fri, 01 Jun 2012 10:35:09 GMT

This release brings you many bug fixes and some new features

Nuget packages:

New features

New PlaceHolderProvider for webforms which will now let you specify exactly where the CSS and JS is rendered, so you can now separate them
*Better support for runtime API changes including changing runtime configuration
Allows for custom formatting of composite file URLs
- new config option: pathUrlFormat="{dependencyId}/{version}/{type}" to have full control of how the composite paths are created
Assemblies now signed with strong names

Bugs fixed

CSS @import directives working (8705,13189)
CSS minify issue (13184)
Machine Name & med trust compatibility (13191)
ResponseFilterStream issue (13188)
Multiple CSS media types (12054)
Ability to specify different render locations of JS/CSS in webforms (12263)
FIPS compliance (13194)
Base64 decoding (13199)
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

The same breaking changes from v1.4 regarding RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile methods are the same
The v1.4 breaking changes regarding config files changes are no longer breaking changes, legacy config will still work however it is recommended to upgrade your config:
- "fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
- "defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
- "providers" element under "compositeFiles" element renamed to "fileProcessingProviders"

Upgrading Umbraco pre v4.8 release

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page

Updated Release: v1.4 (Aug 24, 2011)

Shandem — Thu, 25 Aug 2011 03:56:10 GMT

This release brings you many new features and bug fixes

Nuget packages:

New features

Multiple URL types (each has it's own benefits, for full details see documentation: Composite Url Types)
- mapped id (nice urls)
  - This is now the default. It works by creating a map of the required dependencies on the server before rendering out the html request. The map creates a key which acts as a reference to all of the required dependencies
  - Example: /DependencyHandler.axd/a81e571a8b49102634ad102bc5f1ef40/58/js
- base64 with query strings
  - Example: /DependencyHandler.axd?s=L0Nzcy9DdXN0b21Db250cm9sLmNzczsvQ3NzL0Nvbn RlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7&t=Css&cdv=58
- base64 with paths
  - Example: /DependencyHandler.axd/L0Nzcy9DdXN0b21Db250cm9sLmN zczsvQ3NzL0NvbnRlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7/58/css
Dependency grouping
- We now supporting specifying a group number for dependencies. This is very useful to ensure that client side caching is working at its optimum for for common dependencies that exist between pages.
External/CDN dependencies
- You can use CDF to include external or CDN dependencies such as getting jQuery from the Microsoft of Google CDN. Even though this dependency has been registered with CDF, it will make sure that it's rendered in your html markup in the correct order with regards to all of your other dependencies with a separate script/link tag resolving to the external path
Html Attributes
- Now supporting MVC style HTML attributes with new { .. } object syntax so you can specify any html attributes for any dependency (i.e media="print")

Bugs fixed

Server.Transfer issue (13172
ETag generation issue (13171)
ETag formatting issues (13182, 13183)
Dependency groups issue (13169)
CSS Min (13181)
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

"fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
"defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
"providers" element under "compositeFiles" element renamed to "fileProcessingProviders"
Breaking provider changes: With the new Html attribute feature, the provider method signatures: RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile have changed.

Upgrading Umbraco

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page

Released: v1.4 (Aug 24, 2011)

Thu, 25 Aug 2011 03:56:10 GMT

This release brings you many new features and bug fixes

Nuget packages:

New features

Multiple URL types (each has it's own benefits, for full details see documentation: Composite Url Types)
- mapped id (nice urls)
  - This is now the default. It works by creating a map of the required dependencies on the server before rendering out the html request. The map creates a key which acts as a reference to all of the required dependencies
  - Example: /DependencyHandler.axd/a81e571a8b49102634ad102bc5f1ef40/58/js
- base64 with query strings
  - Example: /DependencyHandler.axd?s=L0Nzcy9DdXN0b21Db250cm9sLmNzczsvQ3NzL0Nvbn RlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7&t=Css&cdv=58
- base64 with paths
  - Example: /DependencyHandler.axd/L0Nzcy9DdXN0b21Db250cm9sLmN zczsvQ3NzL0NvbnRlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7/58/css
Dependency grouping
- We now supporting specifying a group number for dependencies. This is very useful to ensure that client side caching is working at its optimum for for common dependencies that exist between pages.
External/CDN dependencies
- You can use CDF to include external or CDN dependencies such as getting jQuery from the Microsoft of Google CDN. Even though this dependency has been registered with CDF, it will make sure that it's rendered in your html markup in the correct order with regards to all of your other dependencies with a separate script/link tag resolving to the external path
Html Attributes
- Now supporting MVC style HTML attributes with new { .. } object syntax so you can specify any html attributes for any dependency (i.e media="print")

Bugs fixed

Server.Transfer issue (13172
ETag generation issue (13171)
ETag formatting issues (13182, 13183)
Dependency groups issue (13169)
CSS Min (13181)
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

"fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
"defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
"providers" element under "compositeFiles" element renamed to "fileProcessingProviders"
Breaking provider changes: With the new Html attribute feature, the provider method signatures: RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile have changed.

Upgrading Umbraco

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page

Updated Release: v1.4 (Aug 24, 2011)

Shandem — Thu, 25 Aug 2011 03:55:52 GMT

This release brings you many new features and bug fixes
Nuget packages:

New features

Multiple URL types (each has it's own benefits, for full details see documentation: Composite Url Types)
- mapped id (nice urls)
  - This is now the default. It works by creating a map of the required dependencies on the server before rendering out the html request. The map creates a key which acts as a reference to all of the required dependencies
  - Example: /DependencyHandler.axd/a81e571a8b49102634ad102bc5f1ef40/58/js
- base64 with query strings
  - Example: /DependencyHandler.axd?s=L0Nzcy9DdXN0b21Db250cm9sLmNzczsvQ3NzL0Nvbn RlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7&t=Css&cdv=58
- base64 with paths
  - Example: /DependencyHandler.axd/L0Nzcy9DdXN0b21Db250cm9sLmN zczsvQ3NzL0NvbnRlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7/58/css
Dependency grouping
- We now supporting specifying a group number for dependencies. This is very useful to ensure that client side caching is working at its optimum for for common dependencies that exist between pages.
External/CDN dependencies
- You can use CDF to include external or CDN dependencies such as getting jQuery from the Microsoft of Google CDN. Even though this dependency has been registered with CDF, it will make sure that it's rendered in your html markup in the correct order with regards to all of your other dependencies with a separate script/link tag resolving to the external path
Html Attributes
- Now supporting MVC style HTML attributes with new { .. } object syntax so you can specify any html attributes for any dependency (i.e media="print")

Bugs fixed

Server.Transfer issue (13172
ETag generation issue (13171)
ETag formatting issues (13182, 13183)
Dependency groups issue (13169)
CSS Min (13181)
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

"fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
"defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
"providers" element under "compositeFiles" element renamed to "fileProcessingProviders"
Breaking provider changes: With the new Html attribute feature, the provider method signatures: RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile have changed.

Upgrading Umbraco

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page

Updated Release: v1.4 (Aug 24, 2011)

Shandem — Thu, 25 Aug 2011 03:20:19 GMT

This release brings you many new features and bug fixes

New features

Multiple URL types (each has it's own benefits, for full details see documentation: Composite Url Types)
- mapped id (nice urls)
  - This is now the default. It works by creating a map of the required dependencies on the server before rendering out the html request. The map creates a key which acts as a reference to all of the required dependencies
  - Example: /DependencyHandler.axd/a81e571a8b49102634ad102bc5f1ef40/58/js
- base64 with query strings
  - Example: /DependencyHandler.axd?s=L0Nzcy9DdXN0b21Db250cm9sLmNzczsvQ3NzL0Nvbn RlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7&t=Css&cdv=58
- base64 with paths
  - Example: /DependencyHandler.axd/L0Nzcy9DdXN0b21Db250cm9sLmN zczsvQ3NzL0NvbnRlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7/58/css
Dependency grouping
- We now supporting specifying a group number for dependencies. This is very useful to ensure that client side caching is working at its optimum for for common dependencies that exist between pages.
External/CDN dependencies
- You can use CDF to include external or CDN dependencies such as getting jQuery from the Microsoft of Google CDN. Even though this dependency has been registered with CDF, it will make sure that it's rendered in your html markup in the correct order with regards to all of your other dependencies with a separate script/link tag resolving to the external path
Html Attributes
- Now supporting MVC style HTML attributes with new { .. } object syntax so you can specify any html attributes for any dependency (i.e media="print")

Bugs fixed

Server.Transfer issue (13172
ETag generation issue (13171)
ETag formatting issues (13182, 13183)
Dependency groups issue (13169)
CSS Min (13181)
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

"fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
"defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
"providers" element under "compositeFiles" element renamed to "fileProcessingProviders"
Breaking provider changes: With the new Html attribute feature, the provider method signatures: RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile have changed.

Upgrading Umbraco

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page

Released: v1.4 (Aug 24, 2011)

Thu, 25 Aug 2011 03:20:18 GMT

This release brings you many new features and bug fixes

New features

Multiple URL types (each has it's own benefits, for full details see documentation: Composite Url Types)
- mapped id (nice urls)
  - This is now the default. It works by creating a map of the required dependencies on the server before rendering out the html request. The map creates a key which acts as a reference to all of the required dependencies
  - Example: /DependencyHandler.axd/a81e571a8b49102634ad102bc5f1ef40/58/js
- base64 with query strings
  - Example: /DependencyHandler.axd?s=L0Nzcy9DdXN0b21Db250cm9sLmNzczsvQ3NzL0Nvbn RlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7&t=Css&cdv=58
- base64 with paths
  - Example: /DependencyHandler.axd/L0Nzcy9DdXN0b21Db250cm9sLmN zczsvQ3NzL0NvbnRlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7/58/css
Dependency grouping
- We now supporting specifying a group number for dependencies. This is very useful to ensure that client side caching is working at its optimum for for common dependencies that exist between pages.
External/CDN dependencies
- You can use CDF to include external or CDN dependencies such as getting jQuery from the Microsoft of Google CDN. Even though this dependency has been registered with CDF, it will make sure that it's rendered in your html markup in the correct order with regards to all of your other dependencies with a separate script/link tag resolving to the external path
Html Attributes
- Now supporting MVC style HTML attributes with new { .. } object syntax so you can specify any html attributes for any dependency (i.e media="print")

Bugs fixed

Server.Transfer issue (13172
ETag generation issue (13171)
ETag formatting issues (13182, 13183)
Dependency groups issue (13169)
CSS Min (13181)
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

"fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
"defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
"providers" element under "compositeFiles" element renamed to "fileProcessingProviders"
Breaking provider changes: With the new Html attribute feature, the provider method signatures: RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile have changed.

Upgrading Umbraco

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page

Updated Release: v1.4 (Aug 24, 2011)

Shandem — Thu, 25 Aug 2011 03:18:49 GMT

This release brings you many new features and bug fixes

New features

Multiple URL types (each has it's own benefits, for full details see documentation: Composite Url Types)
- mapped id (nice urls)
  - This is now the default. It works by creating a map of the required dependencies on the server before rendering out the html request. The map creates a key which acts as a reference to all of the required dependencies
  - Example: /DependencyHandler.axd/a81e571a8b49102634ad102bc5f1ef40/58/js
- base64 with query strings
  - Example: /DependencyHandler.axd?s=L0Nzcy9DdXN0b21Db250cm9sLmNzczsvQ3NzL0Nvbn RlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7&t=Css&cdv=58
- base64 with paths
  - Example: /DependencyHandler.axd/L0Nzcy9DdXN0b21Db250cm9sLmN zczsvQ3NzL0NvbnRlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7/58/css
Dependency grouping
- We now supporting specifying a group number for dependencies. This is very useful to ensure that client side caching is working at its optimum for for common dependencies that exist between pages.
External/CDN dependencies
- You can use CDF to include external or CDN dependencies such as getting jQuery from the Microsoft of Google CDN. Even though this dependency has been registered with CDF, it will make sure that it's rendered in your html markup in the correct order with regards to all of your other dependencies with a separate script/link tag resolving to the external path
Html Attributes
- Now supporting MVC style HTML attributes with new { .. } object syntax so you can specify any html attributes for any dependency (i.e media="print")

Bugs fixed

Server.Transfer issue (13172
ETag generation issue (13171)
ETag formatting issues (13182, 13183)
Dependency groups issue (13169)
CSS Min (13181)
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

"fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
"defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
"providers" element under "compositeFiles" element renamed to "fileProcessingProviders"
Breaking provider changes: With the new Html attribute feature, the provider method signatures: RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile have changed.

Upgrading Umbraco

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page

Updated Release: v1.4 (Aug 24, 2011)

Shandem — Thu, 25 Aug 2011 02:55:38 GMT

This release brings you many new features and bug fixes

New features

Multiple URL types (each has it's own benefits, for full details see documentation: Composite Url Types)
- mapped id (nice urls)
  - This is now the default. It works by creating a map of the required dependencies on the server before rendering out the html request. The map creates a key which acts as a reference to all of the required dependencies
  - Example: /DependencyHandler.axd/a81e571a8b49102634ad102bc5f1ef40/58/js
- base64 with query strings
  - Example: /DependencyHandler.axd?s=L0Nzcy9DdXN0b21Db250cm9sLmNzczsvQ3NzL0Nvbn RlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7&t=Css&cdv=58
- base64 with paths
  - Example: /DependencyHandler.axd/L0Nzcy9DdXN0b21Db250cm9sLmN zczsvQ3NzL0NvbnRlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7/58/css
Dependency grouping
- We now supporting specifying a group number for dependencies. This is very useful to ensure that client side caching is working at its optimum for for common dependencies that exist between pages.
External/CDN dependencies
- You can use CDF to include external or CDN dependencies such as getting jQuery from the Microsoft of Google CDN. Even though this dependency has been registered with CDF, it will make sure that it's rendered in your html markup in the correct order with regards to all of your other dependencies with a separate script/link tag resolving to the external path
Html Attributes
- Now supporting MVC style HTML attributes with new { .. } object syntax so you can specify any html attributes for any dependency (i.e media="print")

Bugs fixed

Server.Transfer issue (13172
ETag generation issue (13171)
ETag formatting issues (13182, 13183)
Dependency groups issue (13169)
CSS Min (13181)
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

"fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
"defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
"providers" element under "compositeFiles" element renamed to "fileProcessingProviders"
Breaking provider changes: With the new Html attribute feature, the provider method signatures: RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile have changed.

Upgrading Umbraco

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page

Updated Release: v1.4 (Aug 24, 2011)

Shandem — Thu, 25 Aug 2011 02:52:17 GMT

This release brings you many new features and bug fixes

New features

Multiple URL types (each has it's own benefits, for full details see documentation: Composite Url Types)
- mapped id (nice urls)
  - This is now the default. It works by creating a map of the required dependencies on the server before rendering out the html request. The map creates a key which acts as a reference to all of the required dependencies
  - Example: /DependencyHandler.axd/a81e571a8b49102634ad102bc5f1ef40/58/js
- base64 with query strings
  - Example: /DependencyHandler.axd?s=L0Nzcy9DdXN0b21Db250cm9sLmNzczsvQ3NzL0Nvbn RlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7&t=Css&cdv=58
- base64 with paths
  - Example: /DependencyHandler.axd/L0Nzcy9DdXN0b21Db250cm9sLmN zczsvQ3NzL0NvbnRlbnQuY3NzOy9Dc3MvQ29udHJvbHMuY3NzOy9Dc3MvQ29s b3JTY2hlbWUuY3NzOy9Dc3MvU2l0ZS5jc3M7/58/css
Dependency grouping
- We now supporting specifying a group number for dependencies. This is very useful to ensure that client side caching is working at its optimum for for common dependencies that exist between pages.
External/CDN dependencies
- You can use CDF to include external or CDN dependencies such as getting jQuery from the Microsoft of Google CDN. Even though this dependency has been registered with CDF, it will make sure that it's rendered in your html markup in the correct order with regards to all of your other dependencies with a separate script/link tag resolving to the external path
Html Attributes
- Now supporting MVC style HTML attributes with new { .. } object syntax so you can specify any html attributes for any dependency (i.e media="print")

Bugs fixed

Server.Transfer issue (13172
ETag generation issue (13171)
ETag formatting issues (13182, 13183)
Dependency groups issue (13169)
CSS Min (13181)
and more.... see issue tracker

Breaking changes

There are a few breaking changes, as always, ensure you recompile your codebase and test before deploying.

"fileDependencyExtensions" attribute moved from "fileRegistration" element to "clientDependency" element
"defaultProvider" attribute on "compositeFiles" element renamed to "defaultFileProcessingProvider"
"providers" element under "compositeFiles" element renamed to "fileProcessingProviders"
Breaking provider changes: With the new Html attribute feature, the provider method signatures: RenderJsDependencies, RenderCssDependencies, RenderSingleJsFile & RenderSingleCssFile have changed. Though we have backward compatibility methods (Obsolete) still in the codebase, it is advised that you upgrade your providers.

Upgrading Umbraco

See the UpgradingUmbraco.txt referenced in the downloads at the top of this page