Exception in \NeatUpload\UploadHttpModule.cs line 317

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
3/27/2007 9:24:27 AM
Gravatar
Total Posts 488

Exception in \NeatUpload\UploadHttpModule.cs line 317

When I run the site in debug mode (attach to IIS working process), on every request Visual Studio stops with an unhandled exception in this line.

Why is it so? Is that a bug, or do I need to write some config settings?
3/27/2007 10:36:24 AM
Gravatar
Total Posts 148

Re: Exception in \NeatUpload\UploadHttpModule.cs line 317

What are the details of the exception?

--Dean
3/27/2007 10:50:14 AM
Gravatar
Total Posts 488

Re: Exception in \NeatUpload\UploadHttpModule.cs line 317

Trying to debug.
This exception seems to appear when I access the pages like "/default.aspx?page=0" and on postbacks, and does not occur when accessing pages by friendly urls.

The details are below.


System.Web.HttpException was unhandled by user code
Message="Cannot get the query string."
Source="System.Web"
ErrorCode=-2147467259
StackTrace:
at System.Web.Hosting.ISAPIWorkerRequest.GetQueryString()
at System.Web.Hosting.ISAPIWorkerRequest.GetRawUrl()
at System.Web.HttpRequest.get_RawUrl()
at Brettle.Web.NeatUpload.UploadHttpModule.Application_BeginRequest(Object sender, EventArgs e) in F:\Billing\mojoPortal SVN\NeatUpload\UploadHttpModule.cs:line 317
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
3/27/2007 1:05:58 PM
Gravatar
Total Posts 148

Re: Exception in \NeatUpload\UploadHttpModule.cs line 317

What version of mojoPortal are you using?
--Dean
3/27/2007 1:08:59 PM
Gravatar
Total Posts 488

Re: Exception in \NeatUpload\UploadHttpModule.cs line 317

SVN version from /branches/joesandbox2
3/27/2007 3:59:57 PM
Gravatar
Total Posts 148

Re: Exception in \NeatUpload\UploadHttpModule.cs line 317

This is a bug in the version of NeatUpload that is included with mojoPortal.  It is fixed in later versions of NeatUpload.  Until mojoPortal's SVN is updated, the easiest fix is to replace the Brettle.Web.NeatUpload.dll built by mojoPortal with the same assembly from the latest NeatUpload development snapshot (currently NeatUpload-trunk.439.zip).

--Dean
3/27/2007 4:04:50 PM
Gravatar
Total Posts 18439

Re: Exception in \NeatUpload\UploadHttpModule.cs line 317

Hey Dean,

Anything special I need to be aware of in updating? Should I just get your latest, put it under vendor branches then merge it into the solution?

Any architectural changes I need to account for or just swap it out?

Hope things are going well for you, been meaning to email you.

Cheers,

Joe
3/27/2007 7:31:27 PM
Gravatar
Total Posts 148

Re: Exception in \NeatUpload\UploadHttpModule.cs line 317

Nothing special, no architectural changes that I can think of.  Here's the procedure I've followed in the past:

1. Delete the files (but not directories) under vendor/NeatUpload in your working copy.  So that you have an empty directory tree.  Do not commit yet.
2. Unzip the NeatUpload-trunk.439.zip and copy it into vendor/NeatUpload.
3. Use 'svn status' to check for new files.  I don't think there are any at the moment.
4. Commit in vendor/NeatUpload with a log message of "Imported NeatUpload-trunk.439".
5. Merge the changes from you committed to vendor/NeatUpload into branches/joesandbox2/NeatUpload in your working copy but don't commit yet.
6. Merge the changes from you committed to vendor/NeatUpload/NeatUpload into branches/joesandbox2/Web/NeatUpload in your working copy but don't commit yet.  There might not be any changes there, I don't remember.
7. Resolve any conflicts and make sure everything builds/works.
8. Commit in branches/joesandbox2 with a log message of:

svn merge -r REV1:REV2 vendor/NeatUpload branches/2.1.1/NeatUpload
svn merge -r REV1:REV2 vendor/NeatUpload trunk/NeatUpload

where REV1 and REV2 are the revision numbers you used to do the merge in steps 5 and 6.  Those would be the revision of last commit to vendor/NeatUpload before starting the whole process and the revision of the commit you made in step 4. 

The log messages are important because it helps you figure out what you've already merged.

--Dean

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