Here are my test results:
Simulator - Don't link = Works
Simulator - Link SDK = Works
Simulator - Link all = Fails
Device - Don't link = Works
Device - Link SDK = Works
Device - Link all = Fails
I'm not sure on how to move further with this now? Is this a linker issue,
and should I file a
Hello Anders,
On Thu, Feb 16, 2012 at 7:34 AM, andersa anders.ag...@larmia.se wrote:
Here are my test results:
Simulator - Don't link = Works
Simulator - Link SDK = Works
Simulator - Link all = Fails
Device - Don't link = Works
Device - Link SDK = Works
Device - Link all = Fails
I'm
Hi!
My web reference classes are already decorated with the [Preserve]
attribute, and that is a big part of my confusion. I've instructed the
linker to preserve my classes but still they get removed.
I'll put together a test case an file an issue on this.
And I'm going to dig in to the linker
I have a problem when communicating with a web service (ASP.NET 2.0 asmx).
The web service relies on Soap headers to pass some initial authentication
data. Without these, the entire session fails.
When running my MonoTouch app in the simulator everything works great. The
headers are passed from
Hi,
Do you have a test case we can try out? Otherwise it'll probably be
very hard to figure this out.
Thanks,
Rolf
On Tue, Feb 14, 2012 at 11:39 AM, andersa anders.ag...@larmia.se wrote:
I have a problem when communicating with a web service (ASP.NET 2.0 asmx).
The web service relies on Soap
Hi!
I'll try to put together a small enough project to prove this.
//Anders
--
View this message in context:
http://monotouch.2284126.n4.nabble.com/Soap-headers-getting-stripped-away-tp4386644p4386881.html
Sent from the MonoTouch mailing list archive at Nabble.com.
Hello,
Please try to use Don't link on the device (it defaults to Link SDK
assemblies).
You can also try to use Link SDK assemblies on the simulator.
If, by changing both, you get the simulator failing and the device
working the it's likely a linker issue and we'll need a test case to
correct
