wapl Forum Rss Feed

New Post: Problems with signed assemblies

grahamdyson — Mon, 08 Sep 2008 10:54:09 GMT

Hi Graham,

Thanks for the complements about the project, when I originally figured out how to implement this it was such a headache I thought there must be other people out there wanting to do the same. From the activity here on CodePlex, it seems remain forever unknown!

Its going to be problematic to get signing working with WAPL due to using the VS/msbuild built assembly and building its own extra assembly then merging the two. So the VS/msbuild built assembly can't be signed, instead I would have thought that the merged assembly would need to be signed in the post build step (obviously after the merging has taken place!).

Hope that helps,
Graham D

New Post: Problems with signed assemblies

grahamt — Mon, 08 Sep 2008 09:29:20 GMT

Hi,

First off let me say that I think this is a really efficient solution (once you get your head around it :) ) to getting around embedding asp.net resources into a easily distributable dll. I'm really surprised more people aren't aware of this.

I'm at a position now where I want to place the resulting Dll to the GAC but I have encountered a problem with signing the assembly. On building the project the WAPL tool crashes complaining that one or more assemblies are not signed. Now, inspecting through Reflector the Dlls I see that the temporary dlls (that are to be merged) are in fact not signed. Am I missing something? I'm thinking I may need to sign the assembly post build, before the merging takes place.

Any help would be really appreciated.

Thanks

Graham

NEW POST: Visual Studio 2008 Support

grahamdyson — Thu, 10 Apr 2008 23:33:13 GMT

One thing to bare in mind is when using the WAPL Tool with Windows Vista you may need to run Visual Studio as Administrator otherwise you will have problems with access being denied to your own assemblies.

NEW POST: Visual Studio 2008 Support

grahamdyson — Wed, 09 Apr 2008 08:59:39 GMT

Not that I'm aware of, I've used it successfully with Visual Studio 2008, but not on a project which targets .Net 3.5 directly (although I have with them in the same solution).

The only problems I've experienced with the newer technologies has been when using it with other projects using Silverlight 2 as it appears to stop the WAPL console app from working correctly.

NEW POST: Visual Studio 2008 Support

scott2 — Tue, 08 Apr 2008 15:05:56 GMT

Are there any changes in .NET 3.5 or Visual Studio 2008 that break this tool?

NEW POST: User control .ascx not processed?

grahamdyson — Tue, 11 Mar 2008 10:42:46 GMT

Hi Nick,

I'm glad you're finding it useful. Yes I'd say that's definitely a good clue, the size of the assembly should have increased after using the WAPL tool to compile and merge in your .ascx's.

Would it be possible for me to have a look at source files and I could give you some pointers on whats going wrong?

My e-mail's grahamdyson@hotmail.com.

NEW POST: User control .ascx not processed?

nickdunn — Mon, 10 Mar 2008 22:28:32 GMT

This feels like the cleanest way yet of including user controls in multiple projects. This is what I'm trying to achieve, but have hit a snag.

A simple Hello World user control is set up, and when included in a page in another project, only Response.Write("Hello World") shows. Any HTML within the .ascx itself doesn't appear. Could it be that the .ascx file isn't being copied across (or something similar?).

My .partial DLL in the bin/Debug is 16kb, yet my DLL in the /wapl/ folder is only 6kb. Could this be a clue?

NEW POST: wapl tool and resource files

berendengelbrecht — Wed, 19 Dec 2007 06:30:15 GMT

I am having the exact same problem as Feryt, any news? Basically the tool crashes if you try to add any resources (global or local) to the web application library. This is a shame, because other than that it is exactly what we were looking for and it offers functionality that appears to be still sorely missing in Visual Studio 2008. However, to make full use of wapl we do need resources, as we are based in Europe and our applications must be multilingual.

I masked the problem by putting a try catch around the offending line in the foreground application:
{"foreach (String userControlVirtualPath in userControlVirtualPaths)
try
{
clientBuildManager.CompileFile(userControlVirtualPath);
}
catch { }"}

However, other than proving that this is the point where the error is raised, there is no benefit: now if I add resources to my WAPL assembly, the caller just gets missing objects. This shows that the background compilation still crashes and now produces an incomplete assembly.

To reproduce the problem
In the demo solution, rightclick "WAPL Test Library" project, select Add > Add ASP.NET Folder > App_LocalResources
This will make the WAPL tool always crash. Remove the folder and it starts working again. App_GlobalResources does not crash with empty folder, but will crash as well if you add some resources in it. Basically I do not see a method to compile resources into a WAPL assembly.

NEW POST: master page in assembly

rbwilliams — Sun, 29 Jul 2007 03:30:21 GMT

Hi Fritz,
I am trying to do the same exact thing, have a seperate masterpage assembly that contains the masterpage files to be used my reference in other applications. the problem I am having is the actual file does not exist in the virtual path and therefore give me an error because it cannot find the masterpage file. Did you ever get this done and if so can you please let me know how you did it.
Thanks

NEW POST: wapl tool and resource files

Feryt — Fri, 20 Apr 2007 12:35:51 GMT

Hi.
I have library compile problem.
Whenever i add "App_LocalResources"(empty or with some file) dir to my WAPL project i get compile error from WAPL.EXE tool:

foreach (String userControlVirtualPath in userControlVirtualPaths)
clientBuildManager.CompileFile(userControlVirtualPath); <----- Object reference not set to an instance of an object

----------------
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories)
at System.Web.Compilation.BuildManager.EnsureFirstTimeDirectoryInit(VirtualPath virtualDir)
at System.Web.Compilation.BuildManager.GetBuildResultFromCacheInternal(String cacheKey, Boolean keyFromVPP, VirtualPath virtualPath, Int64 hashCode)
at System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath)
at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
at System.Web.Compilation.BuildManager.GetCompiledType(VirtualPath virtualPath)
at System.Web.Compilation.BuildManager.GetCompiledType(VirtualPath virtualPath, ClientBuildManagerCallback callback)
at System.Web.Compilation.BuildManagerHost.GetCompiledTypeAndAssemblyName(VirtualPath virtualPath, ClientBuildManagerCallback callback)
at System.Web.Compilation.BuildManagerHost.GetCompiledTypeAndAssemblyName(VirtualPath virtualPath, ClientBuildManagerCallback callback)
at System.Web.Compilation.ClientBuildManager.CompileFile(String virtualPath)
at InSite.WebApplicationProjectUserControlLibraryTool.Program.Main(String[] args) in D:\Coding\My Projects\WAPL\WAPL Tool\Program.cs:line 125

Thnx.
F.

NEW POST: wapl tool and resource files

cmschick — Fri, 30 Mar 2007 06:36:46 GMT

Hi Fritz,

Did you ever get this working? I am doing something similar and cannot get it to work. More specifically, I am marking files as embedded resources but they are not carried over to the final assembly... just in the partial assembly. If you have any pointers that would be cool.

Thanks,

Chris

NEW POST: Updates to Code

cmschick — Thu, 29 Mar 2007 20:16:00 GMT

I would post a dump but since there are no properties... the dump would be blank. I have contacted Microsoft at this point to see what they can tell me about the controls not persisting as web parts.

It's very strange. Here is what I have noticed at this point.

Adding my control tag to the page in the designer creates the control witout problems as long as I don't create that control tag in a web zone. But if I drag and drop the control on the designer to a webzone, it creates it perfectly and it adds an attribute to the control (AppRelativeVirtualPath="~/MyControlName.ascx")

Now, since that control is static, it stays on the page between postbacks and remembers the personalization state of that control. However, when I add a control dynamically in the OnLoad event, it also saves some personalization state but it errors when trying to locate "~/MyControlName.ascx". For some reason, because this is control derives from UserControl, the WebPartManager expects to see a path instead of a type like it does for any other type of control like full blown server control or web part.

My thought is that since it is a standalone compiled control and everthing needed to instiate it is in the assembly, it should be looking for a type and not a Path. Anyway, we'll see what Microsoft comes up with on this one, I hope they find me a solution and don't just blow me off. It sounds like they never thought it would be possible to have an assembly of precompiled user controls. Otherwise, they would have surely thought of this scenario right? In my opinion they should make whatever changes are necessary to support this scenario as this scenario was created using standard coding practices and does not use reflection to force things. The only Reflection I can see is using it to sort of 'auto' command the aspnet_merge.exe utility but that shouldn't raise any eyebrows!

Later

NEW POST: Updates to Code

grahamdyson — Thu, 29 Mar 2007 10:25:15 GMT

Easy mistake to make. I think the project could do with some Visual Studio templates for creating library user controls/web part user controls/pages/master pages.

If you could post a dump of the customProperties you are getting then I might be able to see whats going on. I can't remember why that condition is there and I don't have any code with me at the moment to step through, but I'll take a look later when I'm on my own machine.

Keep at it you'll get there eventually :o)

Graham

cmschick wrote:
Okay, stupid me... I was adding the 'Base' class and not the actual control name class so now I can dynamically load the compiled user controls into a dynamically created catalog at run time and then load them into a zone without problems.

However, I do still have the same problem when revisiting the page. I have your SqlPersonalizationProvider in place but it skips right past all of the controls because the customProperties("DynamicWebPartsShared") is always null. Where and how are you setting that custom property? It seems to me that if the WebPartManager will allow it to load once, it will allow it to load a second time but it just doesn't seem to know where to look.

For example. My test compiled user control is named MyWatchList.ascx. Even if I manipulate the AppRelativeVirtualPath property, when the WebPartManager hits the LoadPersonalizationState it defaults to looking for this control in "~/MyWatchList.ascx"... I see that you have this pretty much figured out (in terms of the virtual path to actual path mapping) in your WebResourceFromPath.cs and the PrecompiledPageFactory.cs classes so I thought you would know how to tackle this one...

Once again, any help you can provide is much, much, much, appreciated!

Thanks,

Chris

NEW POST: Updates to Code

cmschick — Thu, 29 Mar 2007 03:54:57 GMT

Okay, stupid me... I was adding the 'Base' class and not the actual control name class so now I can dynamically load the compiled user controls into a dynamically created catalog at run time and then load them into a zone without problems.

However, I do still have the same problem when revisiting the page. I have your SqlPersonalizationProvider in place but it skips right past all of the controls because the customProperties("DynamicWebPartsShared") is always null. Where and how are you setting that custom property? It seems to me that if the WebPartManager will allow it to load once, it will allow it to load a second time but it just doesn't seem to know where to look.

For example. My test compiled user control is named MyWatchList.ascx. Even if I manipulate the AppRelativeVirtualPath property, when the WebPartManager hits the LoadPersonalizationState it defaults to looking for this control in "~/MyWatchList.ascx"... I see that you have this pretty much figured out (in terms of the virtual path to actual path mapping) in your WebResourceFromPath.cs and the PrecompiledPageFactory.cs classes so I thought you would know how to tackle this one...

Once again, any help you can provide is much, much, much, appreciated!

Thanks,

Chris

NEW POST: Updates to Code

grahamdyson — Wed, 28 Mar 2007 09:10:50 GMT

Good to see your making some progress.

As far as I'm aware AppRelativeVirtualPath is only used by the WebPartManager to work out if the control is authorized. I'd recommend using the control declaratively in a page to check that it works correctly outside of the webpart system and then (still declaratively) in a WebPartManager. You may end up having to inherit from WebPartManager to override some behavour.

Your second problem about revisiting personalization state can be fixed by using the InSite.Web.UI.WebControls.WebParts.SqlPersonalizationProvider class from the InSite.Web.Wapl as your personalizaton provider (or copy the functionality of the SavePersonalization method to your own provider).

Hope that helps,
Graham

cmschick wrote:
Okay, FYI. Setting the AppRelativeVirtualPath="~/MyControlFileName.ascx" works both on the page and and in my custom catalog but for some reason the actual content of the webpart is not there (the user control). Also, Unfortunately it does not work on a second visit to the page after I have added the control from the catalog because it is looking for the path data in saved personalization state... I'll be working on that now but if you have any pointers I'd love to hear them.

Thanks,

Chris

NEW POST: Updates to Code

cmschick — Tue, 27 Mar 2007 18:09:47 GMT

Okay, FYI. Setting the AppRelativeVirtualPath="~/MyControlFileName.ascx" works both on the page and and in my custom catalog but for some reason the actual content of the webpart is not there (the user control). Also, Unfortunately it does not work on a second visit to the page after I have added the control from the catalog because it is looking for the path data in saved personalization state... I'll be working on that now but if you have any pointers I'd love to hear them.

Thanks,

Chris

NEW POST: Updates to Code

cmschick — Tue, 27 Mar 2007 14:54:59 GMT

Okay I got that part figured out (the cannot load type thing). In a VB.NET project the rootnamespace property on the project needs to be blank on the property page because it was appending that to the namespace defined on the user control code behind so I was getting Test.Web.UI.Test.Web.UI in the assembly. So now my precompiled library builds and merges!

I should be good to go now as long as the AppRelativeVirtualPath setting works.... we'll see.

Thanks.

Chris

NEW POST: Updates to Code

cmschick — Tue, 27 Mar 2007 12:01:02 GMT

Hi Graham,

I agree and I think most people have resigned to thinking that including precompiled user controls and page libraries is impossible.

Ah, thanks for the tip on the reference to the precompiled library from the website.

Yes, I am implementing the IWebPart interface on my user controls so that I get a better designer experience on the aspx where these user controls are added to a zone. Basically it just lets me set the properties on the control itself and results in the designer seeing properties like authorizationfilter etc.. as being valid aspx attributes. The other benefit is that the user control is still a user control but plays nicely as a webpart as well.

I appears to me that once the libraries are merged that the virtual path to the control from the main website is "~/MyControl.ascx" so I may try setting the AppRelativeVirtualPath property on the control after I do an Activator.CreateInstance(myControlType) and see if that works. i.e.

UserControl uc1 = Activator.CreateInstance(myControlType);
uc1.AppRelativeVirtualPath = "~/" + myControlType.Name;

What do you think?

Right now I am having problems with the build of my precompiled libary. It is telling me that 'clientBuildManager.CompileFile(userControlVirtualPath)' could not load type Test.Web.UI.MyControlBase. Unfortunately I only have a basic understanding of how it works at this level in the code. So for me personally, what I need to know is the naming conventions. For example, what do each of command line args really mean, and what do they map to? What I mean is, which event args need to match the names of classes, namespaces, and files...? Is there a correlation between the root namespace of Insite.Web and the namespace declared on the user control that is required for the merge process?

Another question I have is... is the Insite.VisualStudio.Wapl project required to get this all working? I see a number of ResolveAssemblyReference.cache files in the project but I'm not really sure what the project itself does. Can you explain that and do I need it to get things working?

Thanks,

Chris

NEW POST: Updates to Code

grahamdyson — Tue, 27 Mar 2007 10:18:05 GMT

Hi Chris,

I think the level of responses may be due to the lack of documentation about the project, having people post their problems is a good way for me to figure out whats needed to know and how to explain it best.

I think a key concept that I need to get across is that the WAPL Tool (which is included as a post-build step in the project libraries properties and runs automatically) actually takes the .partial.dll which visual studio has compiled (in the bin folder) adds the extra information that .aspx/.ascx/*.master files contains and merges them into a new dll in a sub-folder of the project called wapl. Using this other folder stops visual studio getting confused about which dll is which.

So when you are referencing a library project from another web site/web application project you must browse to the .dll in the wapl sub-folder and use not the project itself. Its also wise to set up your solution so it has a dependancy to the library project. This will make it recompile the library project when you compile/run the web site/web application project (this is done automatically when you use a project reference).

I too have tried using web parts, and have found a few extra difficulties with the way microsoft handles them. If a control decends from UserControl it seems to handle them differently and this behavour is burried deep inside their code. I've developed a class in InSite.Web.Wapl called InSite.Web.UI.WebControls.WebParts.SqlPersonalizationProvider which overrides SavePersonalizationState to help correct this.

Although I don't think that will rectify your particular problem of creating them programmatically. Just checking but you are implementing IWebPart on your PrecompiledUserControl classes?

Cheers,
Graham

cmschick wrote:
Hi Graham,

First of all, thank you for the reply and this project. I too am wondering why we don't see more responses, it's very valuable to be able to precompile user controls and pages for site upgrades. Anyway, I am having some trouble understanding how it is all put together. I have been trying to set a break point in the Wapl library but cannot get it to stop on it. I tried removing the reference and adding the library as a project reference but vs complains that a reference already exists.

In the end, I am trying to see how to get the virtual path to my user controls. I am working on a custom WebParts Catalog that reads webpart types from the dlls in the bin at run time and loads them into the catalog. I need to be able to also load user controls (as webparts) that have a base type as "PrecompiledUserControl" to my catalog at run time as well. I am using the WebPartManager.CreatWebPart() and all is working well but it complains about "type usercontrol" requires path argument.... Do you have any idea how I can set the path?

Also, would you mind giving me a brief explanation how I can replicate the release project in a new project? I tried it but for some reason my version of the WAPL Test Library created a InSite.Web.WaplTestLibrary.partial.dll instead of the InSite.Web.WaplTestLibrary.dll. Am I missing something? At what point do I need to run the WAPL Tool?

Thank you in advance for your help.

Chris

NEW POST: Updates to Code

cmschick — Mon, 26 Mar 2007 15:06:42 GMT

Hi Graham,

First of all, thank you for the reply and this project. I too am wondering why we don't see more responses, it's very valuable to be able to precompile user controls and pages for site upgrades. Anyway, I am having some trouble understanding how it is all put together. I have been trying to set a break point in the Wapl library but cannot get it to stop on it. I tried removing the reference and adding the library as a project reference but vs complains that a reference already exists.

In the end, I am trying to see how to get the virtual path to my user controls. I am working on a custom WebParts Catalog that reads webpart types from the dlls in the bin at run time and loads them into the catalog. I need to be able to also load user controls (as webparts) that have a base type as "PrecompiledUserControl" to my catalog at run time as well. I am using the WebPartManager.CreatWebPart() and all is working well but it complains about "type usercontrol" requires path argument.... Do you have any idea how I can set the path?

Also, would you mind giving me a brief explanation how I can replicate the release project in a new project? I tried it but for some reason my version of the WAPL Test Library created a InSite.Web.WaplTestLibrary.partial.dll instead of the InSite.Web.WaplTestLibrary.dll. Am I missing something? At what point do I need to run the WAPL Tool?

Thank you in advance for your help.

Chris