User Profile & Activity

Thomas Albert Member
Page
of 31
Posted: November 27, 2014 7:01 PM

Is "early next week" already over or is it still to come?

The release of Crosslight 3 was announced so many times now:

- October 2014

- Mid November 2014

- Q4 2014

- Early next week

As a developer you always get excited when the release date of a new and awaited version gets near you. When the release date is adjusted to the future you get disappointed.

Deadlines are our daily business and we all exceed our deadlines sometimes. As an announcement "Q4 20014" had been ok for me. If you release it in October, I'm happy and if you release in December its still in time.

You do a great job with the minor product updates. Please, try to do the same with the major updates. I hope the delay won't be much longer and we get a stable and well tested Crosslight 3 soon.

Thanks,

Thomas

Posted: November 23, 2014 10:52 AM

Great. I'm already curious about the new features.

Thanks,
Thomas

Posted: November 23, 2014 10:50 AM

Hello Support,

Thanks for this info.

What version is Crosslight 2.6 (see above)? There are no release notes for Crosslight 2 update 6. Is this build "Crosslight2_0_5000_117"?

Thanks,

Thomas

Posted: November 4, 2014 6:46 AM

Thanks.

Ok. I keep on developing with build 95 until I here anything different from you or Crosslight 3 will be released.

Thanks,

Thomas

Ok. I keep on developing with build 95 until I here anything different from you or Crosslight 3 will be released.

Thanks,

Thomas

Hello Jimmy,

today I installed the latest updates of Xamarin and I run into the same problem as 2 weeks ago.

Building my Android projects with build 96 creates lots of errors (see attached screenshot).

Switching back to build 95 solved the problem. So it seems Xamarin fixed a problem which was fixed on the Crosslight side with build 96 and both fixes don't work well together.

What is your recommendation? Is switching back to build 95 the solution or will there be a build 97?

Thanks,

Thomas

Hello Jimmy,

thanks a lot for this quick fix. I followed your instructions and the sample now works in my environment. A new project created with the project wizard now works, too.

Great. This kind of support is really outstanding.

But it is the third time I ran into such an issue. My strategy so far was "always install the latest versions". I know that Crosslight has many dependencies (Xamarin, Android SDK, Java, ...) which makes it difficult. So what strategy would you suppose for installing product updates? How do you handle this at Intersoft?

Maybe you could publish a kind of requirements list with each update of Crosslight. This list says for example: Crosslight 2 Update 5 works with Xamarin iOS version "xyz" to version "qwe", Xamarin Android version "xyz" to version "qwe". It was tested with Android SDK up to version "23". Please, do not install Mac OSX Yosemite, because there are the following issues.

Just as a proposal. Maybe it would make live easier for us developers and your support.

Thanks,

Thomas

Hello,

me again (please, see the previous two entries of this post for the whole story). I just switched to an older version of my development VM.

The Syncfusion chart sample works on this machine.

So, there must definitely be a problem with the latest versions of Xamarin and/or with the latest Android SDK.

Do you have any news, ideas, solutions for this problem?

Thanks,

Thomas

Hello,

after doing some more investigation, the situation got worse.

Most of my older apps (Android) work. New apps created with Crosslight project wizard (2_0_5000_95) don't work (Android). I get the same error as reported above. An older app which uses the googlemap component (Android) doesn't work, too.

Current installation:

Xamarin 3.7.226.0

Xamarin.Android 4.18.0.38

Xamarin.iOS 8.2.0.0

As mentoined earlier, I updated to the latest versions today. Since then I experienced the problems. But before I worked with Crosslight 2 Update 4.

I hope you have any idea what the problem might be.

Thanks,

Thomas

-------------------------------------------------------

I found this on the Xamarin page:

Known Issues in 4.18.0.30

ACW's. That was accidentally broken.

Workaround: Use ACW names in Layout .axml, not C# type names.

This will be fixed in 4.18.0.32.


All times are GMT -5. The time now is 9:47 PM.
Previous Next