I have no issue with c# .net program

How do you know that? You are not communicating with the pic correct? So how do you know which end is the problem?

 

What that tells me is you learned nothing from that other thread.

You're some detective. Does anything escape your spidey senses?

 

MplabX is not the best IDE / programming tool.. I doesn't report well.. Some compilers delete all the old files so a successful compilation replaces them with new versions... MPLABX however leaves them so an unsuccessful compilation isn't sometimes obvious... The stream of messages and warnings that spew out from the compile process confuses the best of us.... If you are unfamiliar with this it will confuse you...

 

MplabX is not the best IDE / programming tool.. I doesn't report well.. Some compilers delete all the old files so a successful compilation replaces them with new versions... MPLABX however leaves them so an unsuccessful compilation isn't sometimes obvious... The stream of messages and warnings that spew out from the compile process confuses the best of us.... If you are unfamiliar with this it will confuse you...

Huh???

I never had a problem with "old files". I am not even sure what what means.

As for the error messages, yes they can be confusing at times. But that is not the IDE's fault. It is the fault of the compiler. and sometimes the programmer, not knowing how to surpress some of the various warnings.


BTW The compiler is not the TS's problem here,

 

I never had a problem with "old files". I am not even sure what what means.

Err Okay!! Lookup clean and build....

 

Err Okay!! Lookup clean and build....

I have used it and it has been very rare I had to use it. I usually do a clean just before a build of production code for the first time. Other IDEs have the same or similar command. I don't see it as a big deal for the MPLabX IDE.

 

I try not to use MPLABX, but unfortunately the TS has used it.. If he isn't aware that the hex file will still be intact even if the compile fails, well he needs to know... I also know that if there has NEVER been a successful compile, there won't be a hex file..

The funny thing is... I have modified the source code, and it still steps though using the old files...As I said.. I try not to use it.. The IDE has never really been as good as Ver 8.xx.

Until I desperately need it, it'll stay on the back burner..

 

I try not to use MPLABX, but unfortunately the TS has used it.. If he isn't aware that the hex file will still be intact even if the compile fails, well he needs to know... I also know that if there has NEVER been a successful compile, there won't be a hex file..

The funny thing is... I have modified the source code, and it still steps though using the old files...As I said.. I try not to use it.. The IDE has never really been as good as Ver 8.xx.

Until I desperately need it, it'll stay on the back burner..

The TS's problems are way more than the IDE.

 

The TS's problems are way more than the IDE.

Tell me about it.... I spent hours trying to get C# to spit out a serial string... Gave up and now I use Lazarus for my windows endeavours..
The windows comport API is a tad hard to get right... Plus C# is thread safe so without a DDX is difficult to overcome...With Lazarus you just lob the serial module in the direction of your project and it just works....