Featured post

c# - Usage of Server Side Controls in MVC Frame work -

i using asp.net 4.0 , mvc 2.0 web application. project requiremrnt have use server side control in application not possibl in noraml case. ideally want use adrotator control , datalist control. i saw few samples , references in codepleax mvc controllib howwver found less useful. can tell how utilize theese controls in asp.net application along mvc. note: please provide functionalities related adrotator , datalist controls not equivalent functionalities thanks in advace. mvc pages not use normal .net solution makes use of normal .net components impossible. a normal .net page use event driven solution call different methods service side mvc use actions , view completly different way handle things. also, mvc not use viewstate normal .net controlls require. found article discussing mixing of normal .net , mvc.

c - Cross-platform (microcontroller-PC) algorithm development -


i asked develop algorithm network application on c. project developed on linux pc , transferred more portable platform, include microcontroller. there many microcontroller/companies out there provide nice , large libraries tcp/ip. software hold statistics on network performance.

the whole idea of cross platform (uc - pc) seems rubbish me cause code should written in more platform specific way microcontroller, not expert judge anyway.

is there clever way of doing or there did before? brainstorming has "wrapper library" , "matlab"... ideas?

thx!

i agree extent - want target system , system on developing in interim should close possible (it better if can match). nevertheless idea cross-platform started firmware development while hardware being designed. instead of doing on linux - use embedded os simulator. here steps
- step 1: identify os embedded system; make sure os has simulator runs on pc (win or linux) typical embedded os simulator include vxworks, μc/os-ii, qnx, uclinux ... agreeing on os means hardware design team knows os right match hardware being designed , there consensus hardware + os + application being designed meet requirements of system being developed.
- step 2: use simulator develop application until hardware being designed brought up.
- step 3: once first version of hardware ready , has been powered - can run application minimum changes - no changes code, changes linker/library being used likely.

the idea of cross-platform if done correct has immense advantages - helps remove serializing project development activities.

given mention tcp/ip application - check berkeley sockets support , use it. api should not matter if using simulator, in extreme case if have change os whatever reason berkeley sockets based application better portable.


Comments

Popular posts from this blog

c# - Usage of Server Side Controls in MVC Frame work -

cocoa - Nesting arrays into NSDictionary object (Objective-C) -

ios - Very simple iPhone App crashes on UILabel settext -