PageMethods

NEW POST: Virtual directory and NavigateUrl

fabrice — Mon, 26 May 2008 15:32:12 GMT

Hello Carl,

Some quick questions to help determine what can be the reason for this behavior:

Is there an UrlFormat attribute on the page method? In this case, what's its value?
Could you copy the Page element that corresponds to the page in PageList.xml?
Could you copy the code for the EditRequest method, which is generated in PageList.xml.cs?
Which version of PageMethods are you using? You can find this information in PageList.xml, PageList.xml.cs or in the menu under "Tools | PageMethods"

Fabrice

NEW POST: Virtual directory and NavigateUrl

cnelson1 — Mon, 26 May 2008 04:50:09 GMT

I have a strange issue with HyperLink.NavigateUrl.

If I create my PageMethod call in Page_Load, it includes the virtual folder. But if I create it somewhere else, like in RowDataBound of a GridView, it does not, so the URL fails to redirect to the correct location.

For example, using url aliasing, this:

protected override void OnLoad(EventArgs e)

{

base.OnLoad(e);

this.requesttHyperLink.NavigateUrl = PageMethods.RequestEdit.EditRequest(108231);

}

produces this url:

http://localhost/myvirtualfolder/Requests/EditRequest/108231.aspx

but this:

protected void myGridView_RowDataBound(object sender, GridViewRowEventArgs e)

{

if (e.Row.RowType == DataControlRowType.DataRow)

{

int requestNumber = Convert.ToInt32(DataBinder.Eval(e.Row.DataItem, "RequestNumber"));

HyperLink link = (HyperLink)e.Row.FindControl("requestNumberHyperLink");

link.Text = requestNumber.ToString();

link.NavigateUrl = PageMethods.

RequestEdit.EditRequest(requestNumber);

}

produces this url:

http://localhost/Requests/EditRequest/108231.aspx

which is missing the "myvirtualfolder" part after localhost, and fails.

Any ideas?

Thanks,
Carl

NEW POST: Encrypting QueryStrings

fabrice — Mon, 12 May 2008 17:38:50 GMT

This is something that I had planned to implement, but I never found the time to do it.
It should be possible to add support for this to PageMethods without too much difficulty. Nobody has volunteered yet to tackle this subject. Would you like to implement it? If so, please contact me.

Fabrice

NEW POST: Encrypting QueryStrings

rggardner — Tue, 08 Apr 2008 11:08:48 GMT

Is it possible to encrypt the query string data so that it is no so easy to tamper with?

e.g.

http://yoursite.com?cust_id=29

becomes

http://yoursite.com?cust_id=Z5fg384bd

As an example .....

http://www.devcity.net/PrintArticle.aspx?ArticleID=47

NEW POST: How to build source

cnelson1 — Thu, 13 Mar 2008 22:36:01 GMT

Okay, I solved my own problem :).

I don't know if it is because I am using Web Application Projects, but once I broke my HttpHandler into two files (xxx.ashx and xxx.ashx.cs) the PageMethods generator no longer dumped the Methods section of the PageList.xml.

YAHOO!!!

The only complaints I have so far are:
1) you cannot use constants in the attributes. For example, the UrlFormat and ParamName values cannot contain const values, "ParamName(SomeConst)". However, this is a very minor annoyance and is just a matter of stylistic coding. And, to be honest, I don't think Microsoft attributes allow constants either.

2) The PageList.xml and PageList.xml.cs files cannot be excluded and get regenerated on every build. I understand how this would be a difficult issue to solve, but I do hope you can come up with some solution. The problem is that I am forced to check out these files every build and that means no one else on the team can build that project, unless we do something funky like allow multiple checkouts or just have everyone change the file attribute to writable. Certainly these are workarounds, but it would be nice if they weren't needed.

In any case, I do love this tool and will be using it consistently from now on.

Thanks,
Carl

NEW POST: How to build source

cnelson1 — Thu, 13 Mar 2008 19:56:04 GMT

Well, I guess I can't use PageMethods, since I can't figure out how to stop the generator from deleting my method tags in an HttpHandler file.

Too bad, becuase I love the concept.

Thanks,
Carl

NEW POST: How to build source

cnelson1 — Sun, 09 Mar 2008 00:20:36 GMT

I don't know if this is the correct solution, but I solved it by deleting the registry hive for 8.0.

But I have another question. I am using an HttpHandler with PageMethods. The Method tag keeps disappearing from my PageList.xml and I have to paste it back in to avoid a "method not found" error.

Anyone have any idea why this keeps happening?

NEW POST: How to build source

cnelson1 — Thu, 06 Mar 2008 16:59:06 GMT

Hi.

I tried to build the latest source which includes VS 2008 support and other fixes. The build fails with "Unable to build registry value" errors on the 8.0 key values in the Setup.vdproj file. What is the process to get the build to succeed?

Thanks,
Carl

COMMENTED FEATURE: Add support for VS 2008

fabrice — Wed, 23 Jan 2008 00:43:09 GMT

Add initial support for Visual Studio 2008 (Orcas). Target is Orcas Beta 2, but the work can be started with Beta 1.
Comments: ** Comment from web user: fabrice **

Thanks for the tip azote. For information, this was already included in the source code in July. It's true that no release include this changes yet though.
The .reg file for VS 2008 can be found here: http://www.codeplex.com/PageMethods/SourceControl/DirectoryView.aspx?SourcePath=%24%2fPageMethods%2fSource%2fPageMethods2005%2fSetup&changeSetId=3483

COMMENTED FEATURE: Add support for VS 2008

azote — Tue, 22 Jan 2008 19:16:58 GMT

Add initial support for Visual Studio 2008 (Orcas). Target is Orcas Beta 2, but the work can be started with Beta 1.
Comments: ** Comment from web user: azote **

I can't access that page on ChrisdoesDev.com.... but this is how I manage to got it working:
http://carlosrivero.com/how-to-use-page-methods-with-visual-studio-2008

NEW POST: How to use PageMethods and SVN together

colum — Tue, 20 Nov 2007 18:28:43 GMT

Marco,

Thanks for replying. Alas, it is not possible to exclude like this in TFS, afaik anyway. We've gone down our own methods anyway as we've some legacy code to support that would prove tricky with this approach. I would definitely consdier it for other projects, especially ones I use SVN with.

On a note of pedantry, you stated the exact opposite in your first post, but it gave the right idea anyway. I'd tried both ways, i.e. with .cs or just .xml.

Thanks,
Colum

NEW POST: How to use PageMethods and SVN together

iCmvf — Thu, 15 Nov 2007 18:33:07 GMT

Hello flcdrg and colum,

you do not have to exclude PageList.xml but only PageList.xml.cs.

Then the metadata stays in the source repository, but the code generated fom it not. And of course, do not mix up excluding from the Visual Studio project or solution with exclduding from source control (SVN or TFS). I do not know TFS in detail and therefore not, if it is possible to exclude files from being controlled as it is with SVN, but it should be.

Hope this helps.

Marco

COMMENTED ISSUE: Only update pagelist.xml if necessary

fabrice — Thu, 15 Nov 2007 10:29:47 GMT

When rebuilding pagelist.xml, consider caching it in memory and comparing it to the on-disk version (eg use a hash of some kind)

Only write to disk if they are different.
Comments: ** Comment from web user: fabrice **

I have ideas for quick wins on this. I'll try to implement them very soon.

NEW POST: How to use PageMethods and SVN together

colum — Thu, 15 Nov 2007 09:55:14 GMT

I am also using TFS and Web Application Project (WAP). This frequent editing issue does seem to be a deal breaker for my use of PageMethods, which otherwise seem great.

Excluding PageList.xml does not work in that it doesn't allow WAP to then compile because this and the .cs file are nested and get excluded together.

Is there any work being done against issues 2492 or 2493? Do you see much more work being done on this? And yes, I know that if you want something done well, you're best doing it yourself. Unfortunately I simply haven't the time now. Will keep an eye on this and see how it goes.

Colum
ps - I know SVN and think it is great, however so is TFS (to preempt a my technology is better than yours response;)

NEW POST: Question on licensing when including in install program file

fabrice — Wed, 24 Oct 2007 11:34:58 GMT

Hello,

I'm not an expert in licenses. I chose the Ms-CL license because it seemed simple. Well, it looks that either it's too simple or too restrictive.
In any case, I don't intend to refrain anyone from packaging the PageMethods DLL in zip of msi archives.

By the way, Microsoft's licenses have just been approved by the OSI. At this occasion, the license names have changed. The Microsoft Community License (Ms-CL) is now the Microsoft Reciprocal License (Ms-RL). I've reflected that for PageMethods on CodePlex.

As far as I can tell, the content of the license has not changed. Only the name.
The following page has more information about the license, but it is even more confusing: http://www.microsoft.com/resources/sharedsource/licensingbasics/sharedsourcelicenses.mspx#ERC
I hope Microsoft will be able to clear this up. Otherwise, I'll have to add a special note to address this kind of common requirement.

Regards,
Fabrice

Project License Changed

Wed, 24 Oct 2007 11:31:27 GMT

Microsoft Reciprocal License (Ms-RL) This license governs use of the accompanying software. If you use the software, you accept this license. If you do not accept the license, do not use the software. 1. Definitions The terms "reproduce," "reproduction," "derivative works," and "distribution" have the same meaning here as under U.S. copyright law. A "contribution" is the original software, or any additions or changes to the software. A "contributor" is any person that distributes its contribution under this license. "Licensed patents" are a contributor's patent claims that read directly on its contribution. 2. Grant of Rights (A) Copyright Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free copyright license to reproduce its contribution, prepare derivative works of its contribution, and distribute its contribution or any derivative works that you create. (B) Patent Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free license under its licensed patents to make, have made, use, sell, offer for sale, import, and/or otherwise dispose of its contribution in the software or derivative works of the contribution in the software. 3. Conditions and Limitations (A) Reciprocal Grants- For any file you distribute that contains code from the software (in source code or binary format), you must provide recipients the source code to that file along with a copy of this license, which license will govern that file. You may license other files that are entirely your own work and do not contain code from the software under any terms you choose. (B) No Trademark License- This license does not grant you rights to use any contributors' name, logo, or trademarks. (C) If you bring a patent claim against any contributor over patents that you claim are infringed by the software, your patent license from such contributor to the software ends automatically. (D) If you distribute any portion of the software, you must retain all copyright, patent, trademark, and attribution notices that are present in the software. (E) If you distribute any portion of the software in source code form, you may do so only under this license by including a complete copy of this license with your distribution. If you distribute any portion of the software in compiled or object code form, you may only do so under a license that complies with this license. (F) The software is licensed "as-is." You bear the risk of using it. The contributors give no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this license cannot change. To the extent permitted under your local laws, the contributors exclude the implied warranties of merchantability, fitness for a particular purpose and non-infringement.

NEW POST: Question on licensing when including in install program file

jk812 — Thu, 11 Oct 2007 09:56:59 GMT

We are planning to use PageMethods.dll (as a standalone, unchanged file) in a commercial product and there seems a little ambiguity in the license, which I hope someone might comment on or clear up.

The license says: "For any file you distribute that contains code from the software (in source code or binary format), you must provide recipients the source code to that file along with a copy of this license, which license will govern that file. You may license other files that are entirely your own work and do not contain code from the software under any terms you choose."

We are distributing the PageMethods.dll file and lots of our own files that call it and do other things. So on one level this seems clear.

However in order to distribute the program, we are wrapping all the files into an install program (PageMethods.dll and a series of other files) in a conventional way. My concern is that we are then making a larger file which itself includes PageMethods and so to use this program, we'd have to provide the source to everything else, just because we are making a file that installs it all together. So potentially we'd have to distribute PageMethods.dll as one file and the rest of our product as another file (which would be a pain for users).

I'm sure that this is not intended, and that lots of other people who use PageMethods.dll and other Microsoft community license programs provide them in a zip or install program, can anyone comment or help clear this up.

Patch Applied

fabrice — Fri, 06 Jul 2007 14:29:59 GMT

fabrice has applied patch #114.

Comment:
Applied in changeset 3483.

COMMENTED FEATURE: Add support for VS 2008

fabrice — Fri, 06 Jul 2007 14:27:48 GMT

Add initial support for Visual Studio 2008 (Orcas). Target is Orcas Beta 2, but the work can be started with Beta 1.
Comments: Associated with changeset 3483.

Source code checked in

fabrice — Fri, 06 Jul 2007 14:27:47 GMT

Added initial support for VS 2008. Code is unchanged, only the registration of the add-in has been added.