enba
Apr 16, 2010
  6389
(1 votes)

EPiServer CMS 6 XML documentation files

For all that asked (and for those that didn’t) to have XML documentation files here they are.

Just unpack them in the folder where you referenced dlls are and you’ll have intellisense.

 

Apr 16, 2010

Comments

Sep 21, 2010 10:33 AM

Thanks!

This should really be packed and placed in the bin folder by the installer. No harm to including this in a default installation!

/Fredrik

Frederik Vig
Frederik Vig Sep 21, 2010 10:33 AM

Totally agree with Fredrik! This is so much help for developers working with EPiServer.

Sep 21, 2010 10:33 AM

Hi,

I'm working with EPiServer.Common.Queries and no documentation popup appear. I think XML doc for EPiServer.Common is missing. Can you add it?
/ ngng@ep.se

Please login to comment.
Latest blogs
Create a multi-site aware custom search provider using Search & Navigation

In a multisite setup using Optimizely CMS, searching for pages can be confusing. The default CMS search regardless of search provider does not...

dada | Jun 12, 2025

Tunning Application Insights telemetry filtering in Optimizely

Application Insights is a cloud-based service designed to monitor web applications, providing insights into performance, errors, and user behavior,...

Stanisław Szołkowski | Jun 12, 2025 |

JavaScript SDK v6: Lightest, Most Efficient SDK Yet

Need a faster site and less frontend bloat? JavaScript SDK v6 is here —and it’s the lightest, smartest SDK we’ve ever released for Optimizely Featu...

Sarah Ager | Jun 11, 2025

Boosting Indexing Efficiency: Reindex Pages Directly from Optimizely’s Navigation Pane

There can be various reasons why you might want to trigger indexing or reindexing of a page/node directly from the navigation pane. In my case, we...

Praful Jangid | Jun 11, 2025

How to Get Started with Google Gemini and Imagen in Optimizely CMS

Bringing AI into your editorial workflow has never been easier. With Epicweb’s AI Assistant now supporting Google Gemini and Imagen, editors workin...

Luc Gosso (MVP) | Jun 9, 2025 |

Avoid Field Type Conflicts in Search & Navigation

When using  Optimizely Search & Navigation , reusing the same property name across different content types is fine — as long as the type is...

dada | Jun 5, 2025