.Net Seminar About Orcas

Yesterday I have attended to a .Net seminar at Naples. It was about the newcoming Visual Studio code named Orcas.
What I learnt from the seminar is
  • They will make the new IDE multi targetted. This means you will be able to compile your project against diffrent .Net versions.
  • IDE will support nested masterpages at design time
  • There will be more components for AJAX as expected
  • IntelliSense will be supported for JavaScript also
  • JavaScript debugging will be added.
  • C# will support a Query language against collections.
  • Class extensions will be possible for sealed classes.
  • LINQ= Query language for every source of data.
    -No more strings for writing queries.Compiler will be aware of the query sytax, this will avoid mistyping ,sytax errors etc.
  • ORM-Object Relational Mapping ; There will be OR designer in the IDE for mapping your relational data to your Object domain.

Comments

Post a Comment

Popular posts from this blog

Launching an LOV by clicking a link or button 11g

I needed to launch the LOV by clicking a link and found the below solution.. Basically I have a RichInputListOfValues on my page but it is set to invisible and I am using a commandlink to popup the LOV .. See the code below.. RichInputListOfValues lovComp = getPostingTemplate(); FacesCtrlLOVBinding.ListOfValuesModelImpl lovModel = null; lovModel = (FacesCtrlLOVBinding.ListOfValuesModelImpl)lovComp.getModel(); lovModel.performQuery(lovModel.getQueryDescriptor()); LaunchPopupEvent e = new LaunchPopupEvent(lovComp); e.queue();
Read more

Retrieve BPM composite version from ADF

It is a common scenario that you use the same ADF app for different versions of the BPM flow. In those cases you would like to control the visibility of the new features of the ADF app that supports the BPM flow changes .. Here is the way to read this info from ADF Add below to you page definitions.. <accessorIterator id="scaIterator" MasterBinding="taskIterator" Binds="sca" RangeSize="25" DataControl="Details" BeanClass="Details.scaType"/> <attributeValues IterBinding="scaIterator" id="compositeVersion"> <AttrNames> <Item Value="compositeVersion"/> </AttrNames> </attributeValues>                And then control your features as below, assuming the new button is visible at 1.10 rendered="#{bindings.compositeVersion.inputValue  >= 1.10 }”
Read more