Changes in dfcb3d2: Updated Integrating Izenda (markdown)

				Guides/Integrating-Izenda.md
			
          @@ -12,3 +12,30 @@ When setting up Izenda with your existing web application, you should first deci

           ##Global.asax

          +If you have your own global.asax, you can put your CustomAdHocConfig class inside that file and any settings you need set should be set in there. You can then remove the global.asax in your reporting directory as that will not be required anymore. If you do not have a global.asax and do not plan on using the Izenda global.asax, then you can create the CustomAdHocConfig class in another portion of your application. What matters in the end is that the InitializeReporting method is called before or when your users reach the reporting section of your application.

          +

          +##Default.master

          +

          +Izenda uses a masterpage in order to display the common elements such as the logo and the blue banner that contains the options to design new reports and dashboards. If you're already using a masterpage in your project, you may need to make some decisions about how you want Izenda to display in your application. If you want your masterpage elements to be displayed on your reporting pages, you can modify your masterpage to include the placeholders for the Izenda reporting pages. You can see more about how to customize individual pages by visiting the links below.

          +

          +* [[Report List|http://wiki.izenda.us/API/CodeSamples/ReportList/custom-report-list]]

          +* [[Report Viewer|]]

          +* [[Report Designer|]]

          +* [[Dashboard Viewer|]]

          +* [[Dashboard Designer|]]

          +* [[Instant Reports|]]

          +* [[Settings|http://wiki.izenda.us/API/CodeSamples/Settings/Customizing-Settings-aspx]]

          +

          +##Calling InitializeReporting

          +

          +If you're integrating Izenda into a web application and you get the mysterious error:

          +

          +"The type or namespace name 'global_asax' does not exist in the namespace 'ASP' (are you missing an assembly reference?)"

          +

          +then you will have to go back to all the reporting pages and change the line:

          +

          +```csharp

          +ASP.global_asax.CustomAdHocConfig.InitializeReporting();

          +```

          +

          +You will need to replace 'ASP' with the namespace of your application.

          \ No newline at end of file

...	...	@@ -12,3 +12,30 @@ When setting up Izenda with your existing web application, you should first deci
12	12
13	13	##Global.asax
14	14
	15	+If you have your own global.asax, you can put your CustomAdHocConfig class inside that file and any settings you need set should be set in there. You can then remove the global.asax in your reporting directory as that will not be required anymore. If you do not have a global.asax and do not plan on using the Izenda global.asax, then you can create the CustomAdHocConfig class in another portion of your application. What matters in the end is that the InitializeReporting method is called before or when your users reach the reporting section of your application.
	16	+
	17	+##Default.master
	18	+
	19	+Izenda uses a masterpage in order to display the common elements such as the logo and the blue banner that contains the options to design new reports and dashboards. If you're already using a masterpage in your project, you may need to make some decisions about how you want Izenda to display in your application. If you want your masterpage elements to be displayed on your reporting pages, you can modify your masterpage to include the placeholders for the Izenda reporting pages. You can see more about how to customize individual pages by visiting the links below.
	20	+
	21	+* [[Report List\|http://wiki.izenda.us/API/CodeSamples/ReportList/custom-report-list]]
	22	+* [[Report Viewer\|]]
	23	+* [[Report Designer\|]]
	24	+* [[Dashboard Viewer\|]]
	25	+* [[Dashboard Designer\|]]
	26	+* [[Instant Reports\|]]
	27	+* [[Settings\|http://wiki.izenda.us/API/CodeSamples/Settings/Customizing-Settings-aspx]]
	28	+
	29	+##Calling InitializeReporting
	30	+
	31	+If you're integrating Izenda into a web application and you get the mysterious error:
	32	+
	33	+"The type or namespace name 'global_asax' does not exist in the namespace 'ASP' (are you missing an assembly reference?)"
	34	+
	35	+then you will have to go back to all the reporting pages and change the line:
	36	+
	37	+```csharp
	38	+ASP.global_asax.CustomAdHocConfig.InitializeReporting();
	39	+```
	40	+
	41	+You will need to replace 'ASP' with the namespace of your application.
...	...	\ No newline at end of file