MonoX support board

Start the conversation, ask questions and share tips and solutions with fellow developers.

Non-registered users can only browse through our support boards. Please register now if you want to post your questions. It takes a second and it is completely free. Alternatively, you can log in without registration using your credentials at major sites such as Google, Microsoft Live, OpenId, Facebook, LinkedIn or Yahoo.

Custom project  (Mono Support )

Viewed 12840 time(s), 9 post(s) 5/17/2013 10:49:51 AMby mev9669
mev9669

mev9669

5/17/2013 10:49:51 AM
Hi,

I am trying to create and compile a custom project 

I get the following errors

....\MonoX\T4Templates\Paths.cs' could not be opened ('Unspecified error ') Portal
....\MonoX\T4Templates\RewrittenPaths.cs' could not be opened ('Unspecified error ') Portal

is this because it is missing a dll file?
This content has not been rated yet. 
515 Reputation 67 Total posts
khorvat

khorvat

5/17/2013 11:56:41 AM
No that shouldn't be the case, please let me know if you have the T4 templates in the project ?

Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts
mev9669

mev9669

5/17/2013 1:57:46 PM
Hi rebuild the whole project again and now I am getting the below error. I know it is something to dow ith Localisation and I am not able t o get around it. I have followed your article and created a folder structure.  http://www.mono-software.com/blog/post/Mono/95/Building-a-custom-ASP-NET-project-based-on-MonoX/ . I then copied c:/LocalizationSolution. I added the this as a project in the main solution. and then added a reference to the main web project.

Configuration ErrorDescription: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. 

Parser Error Message: Could not load file or assembly 'MonoX.Localization' or one of its dependencies. The system cannot find the file specified.

Source Error: 

Line 492: <add assembly="System.Runtime.Remoting, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
Line 493: <add assembly="System.Web.Extensions.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
Line 494: <add assembly="MonoX.Localization"/>
Line 495: </assemblies>
Line 496: <expressionBuilders>
This content has not been rated yet. 
515 Reputation 67 Total posts
khorvat

khorvat

5/17/2013 2:07:15 PM
Did you download the custom project form the GitHub ? Please try to use that source and also if localization project is missing then you should also download it from here.

Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts
mev9669

mev9669

5/17/2013 2:34:27 PM
Yes. I have downloaded the custom project and add the Monox.Localization dll file from the MonoX project. But Now I have run into a different error.

Compilation ErrorDescription: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately. 

Compiler Error Message: CS0433: The type 'MonoSoftware.MonoX.Paths' exists in both 'c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\0f0df636\9ad32d6a\assembly\dl3\20c693d6\9bf669a7_0753ce01\ProjectName.Web.DLL' and 'c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\0f0df636\9ad32d6a\assembly\dl3\e8481149\f95b6d64_5f4ace01\MonoX.DLL'

Source Error:

Line 328: #line default
Line 329: #line hidden
Line 330: @__ctrl.Src = global::System.Convert.ToString(MonoSoftware.MonoX.Paths.App_Themes.All.Common.img.ajaxLoader_gif, global::System.Globalization.CultureInfo.CurrentCulture);
Line 331: return @__ctrl;
Line 332: }
This content has not been rated yet. 
515 Reputation 67 Total posts
mev9669

mev9669

5/17/2013 3:46:54 PM
I am trying to refer to this article to solve the issue. But still havent able to solve it. http://www.mono-software.com/Mono/Pages/Discussion/dtopic/6vL3dW5FUkSfEqEeASh7yQ/Why-webparts-on-homepage-keeps-the-user-on-homepage/?dbmpageno=1

It will be really helpfull if you could provide a full working custom sample project Where I can just do few changes like the connection string and it should work. MonoX is great and I really like it only when I use the default installation. But as I was suppose to buy the source code so that we can build custom projects, I will have to rethink about this as there is very less documentation or the documentation is not straight forward. I can see that you use Telerik controls. I would like documentation similar to them. With full details and examples and samples. 
This content has not been rated yet. 
515 Reputation 67 Total posts
khorvat

khorvat

5/20/2013 10:09:37 AM
Let me try to clear few things so you can better understand how to approach the custom development.

- The project you have downloaded is a MonoX Profile sample solution, not the clean MonoX project - bootstrap, so in order to have a clean solution please use the project & solution file found in the following location "/MonoX/Samples/Solution/". To do custom development you don't need to buy source code package you can do everything you need with the free package, there are many sites built on top of free version. We will release a bootstrap via NuGet package very soon so you will be able to jump start the custom development easier.

- You shouldn't include the Paths.tt in your project this is MonoX's class, if you need similar functionality you should copy the T4 template and change the namespace etc.
Compiler Error Message: CS0433: The type 'MonoSoftware.MonoX.Paths' exists in both 'c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\0f0df636\9ad32d6a\assembly\dl3\20c693d6\9bf669a7_0753ce01\ProjectName.Web.DLL' and 'c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\0f0df636\9ad32d6a\assembly\dl3\e8481149\f95b6d64_5f4ace01\MonoX.DLL'
MonoX has been built in a way that developers can use standard ASP.NET techniques in order build custom solutions. To build a custom controls you can use standard ASP.NET approach then just switch to WebParts add a few lines of code to support dynamic instantiation and that's it. Same applies to master pages, pages etc. So I don't see any obstacles there if you need more help let us know.

Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts
mev9669

mev9669

5/20/2013 2:35:10 PM
After many retries that is after recreating the project again and again I finally managed to get it working. thanks for your help Khorvat.
This content has not been rated yet. 
515 Reputation 67 Total posts
khorvat

khorvat

5/20/2013 2:42:22 PM
Np, I hope that this wasn't that hard ... if you find any part of documentation misleading let us know so we can make it better.

Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts