Exception after upgrading to revision 401

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

What operating system were you running when the bug appeared?
What database platform is your site using?
What version of mojoPortal are you running?
What version of .NET do you use?
What steps are necessary to reproduce the issue? Compare expected results vs actual results.

This thread is closed to new posts. You must sign in to post in the forums.

8/26/2010 1:07:04 PM

alkos333

Total Posts 156

View Posts

Exception after upgrading to revision 401

Could not find a part of the path 'C:\Users\me\Documents\Visual Studio 2010\WebSites\mojoportal\Web\App_Themes\default1\theme.skin'.

Source File: C:\Users\me\Documents\Visual Studio 2010\WebSites\mojoportal\Web\Components\mojoThemeVirtualFile.cs Line: 87

[DirectoryNotFoundException: Could not find a part of the path 'C:\Users\me\Documents\Visual Studio 2010\WebSites\mojoportal\Web\App_Themes\default1\theme.skin'.]
System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +224
System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath) +1142
System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share) +83
System.IO.File.OpenRead(String path) +30
mojoPortal.Web.mojoThemeVirtualFile.Open() in C:\Users\me\Documents\Visual Studio 2010\WebSites\mojoportal\Web\Components\mojoThemeVirtualFile.cs:87
System.Web.Hosting.VirtualPathProvider.OpenFile(String virtualPath) +31
System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) +133
System.Web.UI.PageThemeParser.ParseInternal() +144
System.Web.UI.TemplateParser.Parse() +160
System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() +110
System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) +65
System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() +218
System.Web.Compilation.BuildProvidersCompiler.PerformBuild() +40
System.Web.Compilation.ThemeDirectoryCompiler.GetThemeBuildResultType(String themeName) +741
System.Web.Compilation.ThemeDirectoryCompiler.GetThemeBuildResultType(HttpContext context, String themeName) +73
System.Web.UI.Page.InitializeThemes() +8871714
System.Web.UI.Page.PerformPreInit() +38
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +328

Everything worked fine until I pulled the latest source. Why is this happening all of a sudden?

8/26/2010 1:31:53 PM

Joe Audette

Total Posts 18439

View Posts

Re: Exception after upgrading to revision 401

My best guess is you don't have a theme.skin file in your skin folder or if it exists file permissions are not correct on the theme.skin file.

I'm unable to produce the error, but I've added a change revision 403 so that if it fails to get it from the skin folder it will get it from App_Themes/default, that should prevent the error.

There were several fixes made for the virtual path provider for themes about 6 days ago this is the first I've heard of any related errors and there have been hundreds of source code downloads since then. I'm also running the latest build including these changes on this site and on demo.mojoportal.com.

If all else fails I would try rebooting.

Hope it helps,

Joe

8/26/2010 1:46:16 PM

alkos333

Total Posts 156

View Posts

Re: Exception after upgrading to revision 401

Yes, I didn't have theme.skin, but I've never used it in my skin and it always compiled before. Thanks for a slight modification.

8/26/2010 2:02:38 PM

Joe Audette

Total Posts 18439

View Posts

Re: Exception after upgrading to revision 401

In years past we didn't use the theme.skin file for much and they were all almost identical among the included skins but the theme.skin file has become more important in recent times, it is very important for Artisteer skins and the jQueryUI skin where we use properties set in the theme.skin file to determine whether to render extra markup needed for Artisteer or jQuery UI designs.

Best,

Joe

You must sign in to post in the forums. This thread is closed to new posts.