.NET training/support available

[SNOW_MEGA]

Bhayya, bacha anwers kaadu kani bacha questions adigaav nuvvu. Asalu ippudu evaru Interfaces gurunchi adugutunnaru interviews lo? Sare nuvvu adigav kabatti cheptunna. -- Interfaces have some benefits interms of app architecture. If you have common methods across different modules in app (ex: Insert / Update / Delete / Read) we keep them in interface instead of writing in all classes and the classes which does those operations should / would implement by using interfaces. So that across app it looks good interms of architecture. -- In WCF / webservices world, Interfaces are very useful when you are exposing the methods to public. We are not supposed to expose classes or their methods, we keep all methods in interface which supposed to be exposed and we expose interface to the client. -- I never used Interfaces on abstract classes. Nuvvu cheppu nenu telusukunta. Inka command pattern antava, we mainly use that pattern in Windows Forms / WPF apps. It's been very long that i used it but will try to explain. If you want to override the predefined command of a control (button , menu item etc) we use it. In WPF, we create class by implementing ICommand interface and we use INotifyPropertyChanged to trigger the changes in the control. I am pretty sure this command pattern makes the coding very complicated. I know my answer is not 100% perfect but This question is not the deciding factor on my .net knowledge. Aina ippudu andaru Web API, OAuth, AngularJS antu untunte inka interfaces, windows forms, wpf meeda questions enti? Sare nuvvu PRISM, XAML, XAMARIN, Web API vs WCF in REST, OAuth gurunchi explain chey. Andariki Anni Raavu bhayya so stop pulling other legs. Nuvvu antha thopu aithe velli Microsoft vaadiki cheppuko appudu neeku new technology implement cheyamantaru. Dobbeeyyyyy ....

[SNOW_MEGA]

 

7 minutes ago, EzMcSquare said:

SNOW_MEGA

 nee adugu.... :- ) 

 

 

11 minutes ago, kajal said:

Where are the answers?

aaa brother aaa brother cheppandi brother 

[EzMcSquare]

20 minutes ago, SNOW_MEGA said:

Bhayya, bacha anwers kaadu kani bacha questions adigaav nuvvu. Asalu ippudu evaru Interfaces gurunchi adugutunnaru interviews lo? Sare nuvvu adigav kabatti cheptunna. -- Interfaces have some benefits interms of app architecture. If you have common methods across different modules in app (ex: Insert / Update / Delete / Read) we keep them in interface instead of writing in all classes and the classes which does those operations should / would implement by using interfaces. So that across app it looks good interms of architecture. -- In WCF / webservices world, Interfaces are very useful when you are exposing the methods to public. We are not supposed to expose classes or their methods, we keep all methods in interface which supposed to be exposed and we expose interface to the client. -- I never used Interfaces on abstract classes. Nuvvu cheppu nenu telusukunta. Inka command pattern antava, we mainly use that pattern in Windows Forms / WPF apps. It's been very long that i used it but will try to explain. If you want to override the predefined command of a control (button , menu item etc) we use it. In WPF, we create class by implementing ICommand interface and we use INotifyPropertyChanged to trigger the changes in the control. I am pretty sure this command pattern makes the coding very complicated. I know my answer is not 100% perfect but This question is not the deciding factor on my .net knowledge. Aina ippudu andaru Web API, OAuth, AngularJS antu untunte inka interfaces, windows forms, wpf meeda questions enti? Sare nuvvu PRISM, XAML, XAMARIN, Web API vs WCF in REST, OAuth gurunchi explain chey. Andariki Anni Raavu bhayya so stop pulling other legs. Nuvvu antha thopu aithe velli Microsoft vaadiki cheppuko appudu neeku new technology implement cheyamantaru. Dobbeeyyyyy ....

1) about interfaces ... you have no idea.. why the hell they  have been introduced into OOP. Interface is not about exposing classes r not.. Its all about object decoupling. 

 Program to Interface Not implementation  In short ..lo cheppalli antha..Object decoupling.

2) Command pakka.. 100% thappu cheppavu...  i cannnot explain here bcoz I need white board..  ..first to explain..what are the early problems with  Buttons...and which resulted to use command pattern on buttons.

Snow_mega... nee answers... architects vinta...  interview..lo.. select chayaru...your answers tell ..you dont have subject..

end to end... each and every step of control flow medha neeku idea ledu

Emi vachu . .NET neeku.... database loo "roll back." uses command pattern... Operating system..(windows, iOS)... rollback edit..uses command pattern..

Finance world... calculations roll back ki command pattern...

Yes ....I work for Microsoft... .Building number 109 ... Bellevue wa.....  PRISM, WPF antava...Hedge fund companies per day 1000$ pay chasthau...

neeku actual subject raadhu master........

 

anular js..UI coding loo command pattern use chastharu..

WCF,WEB API any r C# middle tier...logic..Object decoupling.. i.e Interface chalaa use chastharu.

Those who dont use interfaces in their code.. they are called..as very very very poor programmers.or freshers..or bacha...r pillalu,,

If i was You.. I will....accept..allegation and will learn... instead of defending....  I will learn...

Infact naa subject levels... and depth ala naa narchukuna