archive-be.com » BE » B » BENNYMICHIELSEN.BE

Total: 348

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Replace MacBook memory – Benny Michielsen
    lock next to the battery to the unlocked position The battery will pop out Remove the battery Use a cross screwdriver to remove the three screws of the plate protecting the memory and the hard disk They are very small so use your smallest screwdriver you can find Next pull the plate away you now have access to the memory By using the lever per memory slot the ram sticks will pop out making place for the new ones Gently push them in until you hear a click Done Author BennyM Posted on 16 12 2008 Categories Computer Tags macbook memory Leave a Reply Cancel reply Your email address will not be published Required fields are marked Comment Name Email Website Post navigation Previous Previous post iPhone Tech Talk Amsterdam Next Next post In search of a mediaserver Search Search for Search Follow me Recent Comments Rick on Partitioning and wildcards in an Azure Data Factory pipeline BennyM on WCF HTTPS And Request Entity Too Large Justin on WCF HTTPS And Request Entity Too Large The Morning Brew Chris Alcock The Morning Brew 2052 on Getting up and running with Mono and Raspberry Pi 3 bhldev on Exposing iCal data

    Original URL path: http://blog.bennymichielsen.be/2008/12/16/replace-macbook-memory/ (2016-04-29)
    Open archived version from archive


  • iPhone Tech Talk Amsterdam – Benny Michielsen
    Development Tools Overview and Programming Concepts Introduction to Objective C and Cocoa Touch Developing iPhone Applications with UIKit Maximizing Your Application s Performance on iPhone Submitting to the App Store using iTunes Connect If you compare this with their original list you see that there were a lot more sessions than originally planned and as a result the speaker had a lot of trouble fitting it all in his schedule Which is disappointing removing two or three topics would have been better especially since there was a lot of overlap between some of them User Interface Design for instance explained all the different controls available and this was repeated again in the UIKit presentation What would have been better was explaining the concepts behind it in the first session and then actually implementing a sample application using the UIKit Model View Controller was also explained three times why not explain it once and show code the second time Knowing the theory behind it is good but actually showing us why some things are in place would have been better Did all this make it a useless event Certainly not if there is one in the future I hope I will be able to attend again and because this was the first time Apple organized something like this they probably still have to learn what content fits and what not And ow yeah catering was excellent Author BennyM Posted on 10 11 2008 Categories Software Development Tags apple iPhone techtalk Leave a Reply Cancel reply Your email address will not be published Required fields are marked Comment Name Email Website Post navigation Previous Previous post Using Spring NET as IoC container for Composite WPF Next Next post Replace MacBook memory Search Search for Search Follow me Recent Comments Rick on Partitioning

    Original URL path: http://blog.bennymichielsen.be/2008/11/10/iphone-tech-talk-amsterdam/ (2016-04-29)
    Open archived version from archive

  • techtalk – Benny Michielsen
    posted on the website The presentations I saw were iPhone Development Overview iPhone User Interface Design iPhone Development Tools Overview and Programming Concepts Introduction to Objective C and Cocoa Touch Developing iPhone Applications with UIKit Maximizing Your Application s Performance on iPhone Submitting to the App Store using iTunes Connect If you compare this with their original list you see that there were a lot more sessions than originally planned and as a result the speaker had a lot of trouble fitting it all in his schedule Which is disappointing removing two or three topics would have been better especially since there was a lot of overlap between some of them User Interface Design for instance explained all the different controls available and this was repeated again in the UIKit presentation What would have been better was explaining the concepts behind it in the first session and then actually implementing a sample application using the UIKit Model View Controller was also explained three times why not explain it once and show code the second time Knowing the theory behind it is good but actually showing us why some things are in place would have been better Did all this make it a useless event Certainly not if there is one in the future I hope I will be able to attend again and because this was the first time Apple organized something like this they probably still have to learn what content fits and what not And ow yeah catering was excellent Author BennyM Posted on 10 11 2008 Categories Software Development Tags apple iPhone techtalk Leave a comment on iPhone Tech Talk Amsterdam Search Search for Search Follow me Recent Comments Rick on Partitioning and wildcards in an Azure Data Factory pipeline BennyM on WCF HTTPS And Request Entity

    Original URL path: http://blog.bennymichielsen.be/tag/techtalk/ (2016-04-29)
    Open archived version from archive

  • Using Spring.NET as IoC container for Composite WPF – Benny Michielsen
    post Dutch alt net Next Next post iPhone Tech Talk Amsterdam Search Search for Search Follow me Recent Comments Rick on Partitioning and wildcards in an Azure Data Factory pipeline BennyM on WCF HTTPS And Request Entity Too Large Justin on WCF HTTPS And Request Entity Too Large The Morning Brew Chris Alcock The Morning Brew 2052 on Getting up and running with Mono and Raspberry Pi 3 bhldev on

    Original URL path: http://blog.bennymichielsen.be/2008/09/17/using-spring-net-as-ioc-container-for-composite-wpf/ (2016-04-29)
    Open archived version from archive

  • composite – Benny Michielsen
    WPF Search Search for Search Follow me Recent Comments Rick on Partitioning and wildcards in an Azure Data Factory pipeline BennyM on WCF HTTPS And Request Entity Too Large Justin on WCF HTTPS And Request Entity Too Large The Morning Brew Chris Alcock The Morning Brew 2052 on Getting up and running with Mono and Raspberry Pi 3 bhldev on Exposing iCal data in WebAPI Archives March 2016 February 2016

    Original URL path: http://blog.bennymichielsen.be/tag/composite/ (2016-04-29)
    Open archived version from archive

  • Dutch alt.net – Benny Michielsen
    fields are marked Comment Name Email Website Post navigation Previous Previous post Adding transactions and exploring the BindingList Next Next post Using Spring NET as IoC container for Composite WPF Search Search for Search Follow me Recent Comments Rick on Partitioning and wildcards in an Azure Data Factory pipeline BennyM on WCF HTTPS And Request Entity Too Large Justin on WCF HTTPS And Request Entity Too Large The Morning Brew

    Original URL path: http://blog.bennymichielsen.be/2008/09/16/dutch-alt-net/ (2016-04-29)
    Open archived version from archive

  • alt.net – Benny Michielsen
    Categories Software Development Tags alt net Leave a comment on Dutch alt net Search Search for Search Follow me Recent Comments Rick on Partitioning and wildcards in an Azure Data Factory pipeline BennyM on WCF HTTPS And Request Entity Too Large Justin on WCF HTTPS And Request Entity Too Large The Morning Brew Chris Alcock The Morning Brew 2052 on Getting up and running with Mono and Raspberry Pi 3

    Original URL path: http://blog.bennymichielsen.be/tag/alt-net/ (2016-04-29)
    Open archived version from archive

  • Adding transactions and exploring the BindingList – Benny Michielsen
    the presenter that is listening had to keep track of the changes and forward them to the webservice when the user wants to save his work The code I ve written for that isn t rocket science or hard to grasp It boils down to what is transferred between the client and the server public enum ChangeType Added 0 Changed Deleted public class TodoEditDto public virtual Guid EditId get set public virtual TodoDto EditedTodo get set public virtual ChangeType ChangeType get set The ChangeType indicates what has happened the item was added changed or deleted The TodoEditDto wraps the edited dto adds a ChangeType and EditId property The EditId is generated on the client and used to identify newly saved objects when the server sends back the Id s that were generated when the todo was persisted That way a new created todo can be edited right away after saving it saved data to server foreach var persistedEdit in response PersistedEdits var foundEdit from edt in editedTodos where edt Value EditId Equals persistedEdit EditId select edt Value First foundEdit EditedTodo Id persistedEdit EditedTodo Id With some basic editing now in place some work is still needed in the UI let s now add transactional support to our save method Spring Net allows you to add this capability declarative or programmatic and even within these two approaches there are several ways to achieve your result At work I ve always used the declarative way using AutoProxy and the Transaction attribute To make that work you need to add a reference to Spring Data add the attribute to the methods that need to be transactional and add the following object definitions to your configuration object id AutoProxyCreator type Spring Aop Framework AutoProxy DefaultAdvisorAutoProxyCreator Spring Aop object id TransactionAdvisor type Spring Transaction Interceptor TransactionAttributeSourceAdvisor Spring Data property name TransactionInterceptor ref TransactionInterceptor object Transaction Interceptor object id TransactionInterceptor type Spring Transaction Interceptor TransactionInterceptor Spring Data property name TransactionManager ref TransactionManager property name TransactionAttributeSource ref AttributeTransactionAttributeSource object object id AttributeTransactionAttributeSource type Spring Transaction Interceptor AttributesTransactionAttributeSource Spring Data object Transaction TransactionPropagation Required public SaveEditedTodosResponse SaveTodos SaveEditedTodosRequest request do stuff At runtime Spring Net will create a proxy for each service that has the tranascation attribute declared on its methods and manage the transaction from in that generated class Everything you ve written will be transactional from that point until the method that is being called is completed For now however let s use the TransactionProxyFactoryObject To use this approach I only need to change my service definition Through the transaction attributes property I can define which methods need to be transactional in this case any method that starts with Save The target property can be any object in your context object id TodoService type Spring Transaction Interceptor TransactionProxyFactoryObject Spring Data property name PlatformTransactionManager ref TransactionManager property name TransactionAttributes name values add key Save value PROPAGATION REQUIRED name values property property name Target object type TodoCore AppService TodoService TodoCore property name TodoRepository ref NhnTodoRepository object property object

    Original URL path: http://blog.bennymichielsen.be/2008/09/05/adding-transactions-and-exploring-the-bindinglist/ (2016-04-29)
    Open archived version from archive