0

I have an app I have been working on that was running fine.

I upgraded to the latest Xamarin with mac support and now I get an error when I try to use HttpUtility.ParseQueryString.

I have an App.config file and it is telling me that it can't parse it, but this happens when trying to call ParseQueryString. How are those 2 related?

I thought I had found the problem because my app also has a ServiceReferences.ClientConfig file for http client settings. I copied my App.config section to the ServiceReferences.ClientConfig file and that fixed it until I went to show my fellow dev the new error.

The new error was saying something about Path.Combine path1 being null.

I looked up that error and found a reference to a page talking about MacSupport in xamarin here: https://searchcode.com/codesearch/view/8556026/

I don't know if they are related, but that is the closest I found to the stack trace I was seeing.

Can anyone tell me what changed in Mono 4.8 for Mac in Xamarin that would cause an issue with HttpUtility.ParseQueryString and how to solve it?

SushiHangover
  • 73,120
  • 10
  • 106
  • 165
user856232
  • 1,073
  • 2
  • 14
  • 40
  • 1
    please post the relevant code and the specific errors/exceptions that you're getting – Jason Mar 13 '17 at 22:06
  • I am not sure what to post that would be helpful. What I ended up doing was just copying the HttpUtility methods that I actually needed an just using the source. I decided there just wasn't any way to get the whole Http system to initialize in my case as an end user app. – user856232 Mar 16 '17 at 14:20

1 Answers1

0

System.Configuration is a common point of pain during mono upgrades, as it's behavior sometimes subtly (or not so subtly) changes.

You'll need to post a much larger chunk of information here for anyone to be able to help you.

Or you could post on the XM Forms or file a bug if you believe this is a bug, as those are a more appropriate place for such reports.

Chris Hamons
  • 1,510
  • 11
  • 22
  • I am not sure what to post that would be helpful. What I ended up doing was just copying the HttpUtility methods that I actually needed an just using the source. I decided there just wasn't any way to get the whole Http system to initialize in my case as an end user app. – user856232 Mar 16 '17 at 14:20
  • That may not be a terrible idea, if your use case is very small. System.Configuration issues can be really painful. – Chris Hamons Mar 16 '17 at 14:25