Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7967129
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 4, 20262026-06-04T06:36:56+00:00 2026-06-04T06:36:56+00:00

Persistence of aspects between compile time and run time is achieved by serializing aspects

  • 0

Persistence of aspects between compile time and run time is achieved by serializing aspects …

From PostSharp Documentation.

For my understanding, this is only important if I use the CompileTimeInitialize method in order to set certain values at compile time. I use this very rarely. I think just instantiating aspects would be much faster then deserializing them, isn’t it? So wouldn’t PostSharp more fast, if I had the option to skip the serialization process?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-04T06:36:58+00:00Added an answer on June 4, 2026 at 6:36 am

    I suppose you’re talking of CompileTimeInitialize. If you don’t need it, you can skip serialization by using MsilAspectSerializer (see http://doc.sharpcrafters.com/postsharp-2.1/Content.aspx/PostSharp-2.1.chm/html/f711d5da-5696-443c-9b42-e67a3d8b7b36.htm http://doc.postsharp.net/postsharp-2.1/Default.aspx##PostSharp-2.1.chm/html/f711d5da-5696-443c-9b42-e67a3d8b7b36.htm).

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I've implemented a repository pattern with persistence ignorance. The repository implementation only interacts with
I'm using persistence API and want to load jdbc URL from web.xml. URL should
I have this persistence unit: <?xml version=1.0 encoding=UTF-8?> <persistence version=1.0 xmlns=http://java.sun.com/xml/ns/persistence xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xsi:schemaLocation=http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd>
persistence.xml looks like this: <persistence-unit name=testPU transaction-type=RESOURCE_LOCAL> <provider>org.hibernate.ejb.HibernatePersistence</provider> <non-jta-data-source>jdbc/test</non-jta-data-source> <jar-file>../../lib/app-services-1.0.jar</jar-file> <exclude-unlisted-classes>false</exclude-unlisted-classes> </persistence-unit> It is
Is it possible to change values in persistence.xml from within the program that is
I'm working on switching my JPA persistence provider from EclipseLink 2.3 to Hibernate 3.6.5.Final.
I am using compile time weaving with aspectj to weave in Spring's transactional code
I am trying to convert my load-time-woven aspectj to compile-time-woven. So I removed <context:load-time-weaver/>
This is my persistence.xml : <persistence> <persistence-unit name=MyUnit> <provider>org.hibernate.ejb.HibernatePersistence</provider> <jta-data-source>jdbc/abcDS</jta-data-source> </persistence-unit> </persistence> This is
I just switched my persistence.xml from <property name=toplink.ddl-generation value=drop-and-create-tables/> to <property name=toplink.ddl-generation value=create-tables/> and

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.