The attachments is not currently working for me !?
I was to post something important I found out today regarding Circular Dependency. I have the images for later when attachments work.
First try I get an Error box telling me a can't set a cyclic referencing (makes sense and I expected it) - BUT - I can then retry it and it lets me do it and the app even runs OK - yes, because I have not use a reference to cause the cyclic part. This is not right however - feels all wrong.
Will send a couple of screen captures when the functionality returns.
Yes, you can trick VS I am sure to be able to use cyclic references, for example by using direct .dll references. Also there's no reason for it to not work at runtime, in VIDE I had been using that in purpose for some time in the past
But it's gonna be a nightmare if you some time need to make big changes to one of the dlls and you change the public interface it has (method names etc), so it should better not be used.
I will try an attachment - fingers crossed .............
Yep! - working now - but definitely wasn't yesterday (later) and this morning either.
Now I am posting in the wrong thread perhaps - BUT - hey! it is working.
In VS 2015 the screen dialog messaging about Circular Dependency showed when it should, but then at another try immediately after (I was trying to get a screen shot for my session eNotes) the error did not get shown and the process of adding the reference went ahead.
I have not got a problem as such, it just feels wrong, as if it should be preventing me from doing this - either that or the red cross icon and the message content should reflect a warning and not an error perhaps ?
Here is what I was trying out :-
And here the 'one-time' message :-
Let me know if you wish me to do any further testing.
I was on the sailing ship.
And your images seem to be working now.
I made one change:
The website uses a component to optimize the performance. It does this by compressing HTML data and doing some magic on the CSS and JS files.
I have set this component to be a little less aggressive.
The HTML is still compressed but some JS/CSS tricks have been disabled.
This seems to do the trick.
XSharp Development Team