|
|
WI54M wrote: how i can do that
By programming a loop. What have you tried?
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
|
You were given fairly detailed instructions on what you're going to have to do the last time you posted this question[^]. It's now up to you to actually write the code.
This space for rent
|
|
|
|
|
test
modified 27-Sep-17 6:46am.
|
|
|
|
|
I am sorry, but we won't do your homework for you. It's set to assess what you know, and to show you what areas you need to do more work on. It's not set to see what others know. If you are having problems with this, talk to your teacher.
This space for rent
|
|
|
|
|
What school? I'd like to point out to your teacher that your assignment sucks and should be shot.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Hi,
I have a C++ executable that consumes c# class library by importing the corresponding .tlb file. All works fine, except when I debug c# assembly by setting C++ executable as an external program, all the breakpoints in c# code says "The breakpoint will not currently be hit. No symbols have been loaded for this document"
FYI, I can debug C++ code, that's attached as an external program.
Below are few steps, I have already tried so far, but have no success.
1. Unregistered c# assembly and registered it back
2. Modified GUID and interface name, registered new assembly manually
Other details...
1. I am on Visual Studio 2010
2. For c# assembly, .NET target framework is 2.0, Register for COM interop is checked
3. I am using Win7 64 Bit version
Please let me know, in case any further details required.
Many Thanks
modified 27-Sep-17 0:34am.
|
|
|
|
|
Visual Studio needs access to the *.pdb file. See here[^] on help how to generate one.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
I want to do a .Select for the rest of the fields: EventStatus, EventReason, and EventDateTime like I'm doing for the TrackingEvent and am not sure how to do that. Richard Deeming was helpful in get me started with this but need help with the rest.
TrackingEventHistory is the root for XML element I'm trying to output. The rest (EventStatus, EventReason, EventDateTime) are "children" within that root. There can be multiple TrackingEventHistory's so I'm trying to create a loop for the root and it's children. I'm not sure if .Select is the best way.
new XElement("TrackingEventHistory",
prc.History.Cast<Saia.Data.General.Shipment.HistoryItem>().Select(item => new XElement("TrackingEventDetail",
new XElement("EventStatus", EventCode.Delivered.ToXml()),
new XElement("EventReason", prc.History),
new XElement("EventDateTime", prc.History))
modified 26-Sep-17 17:31pm.
|
|
|
|
|
Rather than wasting your time getting stuck, posting a question and waiting for a reply, you should take some time to learn the basics of how XLINQ works. Fortunately for you, Sacha Barber wrote an excellent article on this topic. You can find it here[^].
This space for rent
|
|
|
|
|
Would something like this work
var query = (from c in doc.Root.Descendants("TrackingEvent") select c).ToList();
foreach (XElement element in query)
{
new XElement("EventStatus", EventCode.Delivered.ToXml()),
Response.Write(element.Value);
}
|
|
|
|
|
Why not try it and find out?
This space for rent
|
|
|
|
|
If you haven't downloaded it yet, you really should try out Linqpad[^]. Here's guidance[^] on how to query XLinq in it.
This space for rent
|
|
|
|
|
Why interfaces not extended and implemented?
|
|
|
|
|
|
|
Picture this.
You just walked into a room, containing a bunch of people who don't know you, and said "Why interfaces not extended and implemented?" and then you left.
Now, everyone in the room is looking at each other, very confused, having no idea what in the f*** you're blabbering about.
Care to elaborate on what you're asking about? You know, like so someone might be able to answer you.
|
|
|
|
|
Do you really think you are good advisor?
Just look at Griff Sir answer.
if you can't do that then don't touch the message, get back to your seat and do your work.
modified 26-Sep-17 23:48pm.
|
|
|
|
|
So you wanted me to guess at what you meant?
I could have and just as easily got it wrong and answered your "question" with incorrect information.
|
|
|
|
|
dont reply on message again like this.I will call authority. This message is not for people like you. ignore this message.
|
|
|
|
|
Go ahead. Call the police.
Would you like me to hand you the phone? Here you go.[^]
|
|
|
|
|
don't expect from me the person who needs to this will do it.
|
|
|
|
|
I could have sworn you said "I will call authority".
|
|
|
|
|
Interfaces can't be extended because they are a very specific contract, and they contain no base material to override - they cannot define any concrete code at all, they just provide a set of signatures (methods, properties, events) which the implementing class is obliged to create in a concrete form as it's part of the contract.
They can't contain any implementation themselves, because that would make them abstract classes and provide a route to multiple inheritance which C# is absolutely not happy with - because it seriously complicates the source code.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
