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.
3 comments

visual studio 2010 - warning MSB8012 : make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile) -

-

i getting following error when building code.

c:\program files (x86)\msbuild\microsoft.cpp\v4.0\microsoft.cppbuild.targets(990,5): warning msb8012: targetpath(e:\study\fwif\demola\ext-libs\libcommoncpp2-1.6.0\w32\debug\ccgnu2.dll) not match linker's outputfile property value g\capecommon14.dll). may cause project build incorrectly. correct this, please make sure $(outdir), $(targetname) , $(targetext) property values match value specified in %(link.outputfile).

i hope 1 know do.

did upgrade project visual studio 2010 previous version? if so, well-known issue.

visual studio 2010 c++ project upgrade guide http://blogs.msdn.com/b/vcblog/archive/2010/03/02/visual-studio-2010-c-project-upgrade-guide.aspx

warnings during upgrade

here of common warnings may run during conversion:

1) linker output directory

one of warnings may see when upgrading applications msb8012: $(targetpath) , linker’s outputfile property value not match:

  • msb8012: $(targetext) ('.dll') not match linker's outputfile property value 'c:\foo\debug\mfcactivex.ocx' ('.ocx') in project configuration 'debug|win32'. may cause project build incorrectly. correct this, please make sure $(targetext) property value matches value specified in %(link.outputfile).

  • msb8012: $(targetpath) ('c:\foo\debug\mfcactivex.dll') not match linker's outputfile property value 'c:\foo\debug\mfcactivex.ocx' ('c:\foo\debug\mfcactivex.ocx') in project configuration 'debug|win32'. may cause project build incorrectly. correct this, please make sure $(targetpath) property value matches value specified in %(link.outputfile).

    link.outputfile value defined @ linker -> general -> output file on property page. default, value $(outdir)$(targetname)$(targetext), same value of $(targetpath). when convert application previous version, however, there not easy way conversion parse link.outputfile figure out values $(targetname) , $(targetext), different customers may have formatted them in different ways. work around that, decided preserve value of linker.outputfile during conversion. after conversion, $(targetname) default $(projectname). $(targetext) default default extension application type: .dll dynamic library, .lib static library , .exe application. link.outputfile value preserved. warning msb8012 issued in conversion log if link.outputfile , $(targetpath) not same. same warnings when building application.

    $(outdir), $(targetname) , $(targetext) exposed on "general" property page, "output directory", "target name", "target extension", respectively. can manually change values of these properties no longer warning.

  • if project produces import library (linker -> advanced -> import library), may need change output folder of import library after conversion if linker output directory not default output directory. otherwise, generated import lib maybe in different directory linker output.

  • debugging.command set default $(targetpath) after conversion. may need make changes right executable launched upon f5 (debugging) or ctrl + f5 (start without debugging).


Comments

Post a Comment

Popular posts from this blog

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.
Read more

ios - Very simple iPhone App crashes on UILabel settext -

-
i have simple application. have button , label in ib. have ibaction onclick calls settext on label. there's outlet label. connected in ib. crashes app first time in simulator. when launch again, sets text. crashes again next time. crashes on actual device. should simple, i'm not sure i'm doing wrong. thanks. in .h file : #import <uikit/uikit.h> @interface untitledviewcontroller : uiviewcontroller { iboutlet uilabel *label; iboutlet uibutton *button; } @property (nonatomic, retain) uilabel *label; -(ibaction) onclick1: (id) sender; @end and in .m: - (ibaction) onclick1: (id) sender { //[label settext:@"hello world!"]; label.text = @"hello world!"; //[button settitle:@"clicked" forstate:uicontrolstatenormal]; } sorry, i'm new site. how crash log , stack? thanks. edit : while answer technically correct, doesn't answer question @ :( sorry < warning - guess > if you're...
Read more

mysql - Why there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT clause? -

-
why there can 1 timestamp column current_timestamp in default or on update clause? create table `foo` ( `productid` int(10) unsigned not null, `addeddate` timestamp not null default current_timestamp, `updateddate` timestamp not null default current_timestamp on update current_timestamp ) engine=innodb; the error results: error code : 1293 incorrect table definition; there can 1 timestamp column current_timestamp in default or on update clause this limitation, due historical, code legacy reasons, has been lifted in recent versions of mysql: changes in mysql 5.6.5 (2012-04-10, milestone 8) previously, @ 1 timestamp column per table automatically initialized or updated current date , time. restriction has been lifted. timestamp column definition can have combination of default current_timestamp , on update current_timestamp clauses. in addition, these clauses can used datetime column definitions. more information, see automati...
Read more