AEC DevBlog

Revit API is moving to .NET Core 8.0

By Moturi Magati George

Updated on 26^th January 2024

Finally, there is great news for Revit API users.

With the upcoming preview release of the Major Revit update, a significant transition is in the works - Revit is making a remarkable shift from .NET 4.8 to .NET Core 8.0. This pivotal change will be put to the test in the upcoming preview version, with the planned release scheduled for this November.

Why is this transition significant?

The move to .NET Core 8.0 is not merely an incremental update; it's a major evolution of the .NET framework. Contrasting with the former .NET 4.8, .NET Core 8.0 is a more modern, open-source, and cross-platform framework. This transformation introduces an array of enhancements, including a boost in performance, cross-platform compatibility, and a wealth of tools and libraries that will open new doors for developers.

What are the benefits of Migrating to .NET Core 8.0?

This transition is poised to bring about significant improvements for the Revit API community who have been working with .NET 4.8. Many Revit API users have had to resort to downgrading their libraries to make them compatible with the .NET 4.8 framework, ultimately impacting their application's performance and hindering cross-platform programming. With .NET Core 8.0, these users will experience a breath of fresh air, as they can enjoy enhanced performance and develop applications that seamlessly run on multiple operating systems.

Challenges for API developers

There will be a few adjustments for the API developers/ users required to ensure that their current applications are compatible with the new versions of Revit. However, these changes, while initially challenging, are akin to a blessing in disguise. They present an opportunity for developers to modernize and optimize their applications, taking full advantage of the new features and capabilities offered by .NET Core 8.0. As a result, Revit API users will be better equipped to meet the evolving demands of the AEC industry.

In conclusion, the migration of Revit API from .NET 4.8 to .NET Core 8.0 is a significant leap forward that promises improved performance, cross-platform compatibility, and a more dynamic development environment. With the planned major release of Revit just around the corner, developers have an exciting future to look forward to. Embrace this transition and be part of the next chapter in the evolution of Revit API development.

Disclaimer!

Kindly note that the content on this blog is speculative in nature and does not constitute any guarantees or assurances regarding future Revit products or functionality. The information provided is subject to change and there is no certainty that idea will be implemented or come to fruition. For more information about Revit Roadmap and Revit Preview Releases kindly refer to Revit Public Roadmap

How to use ToElements Method correctly

By Moturi Magati George

There have been a couple of questions regarding the usage of ToElements Method while filtering elements using the FilteredElementCollector Class. It is good to note that the ToElements Method in the FilteredElementCollector Class returns the complete set of elements that meet the specified filter criteria as a generic IList.

However, it's worth noting that some members of the Revit API community tend to use the ToElements Method after using the FilteredElementCollector which in turn increases memory usage and slows down the performance of the same.

One reason for using ToElements is to obtain the element count. However, that can also be achieved by calling GetElementCount.

Another and more valid reason is to access the elements in the list by index, e.g., you have 1000 elements in the list and you want to read their data in a specific order, e.g., #999, #1, #998, #2 or whatever. Then, you need the index provided by the list, and cannot just iterate over them on the predefined order provided by the enumerator.

Here are examples that demonstrate the usage of the two:

//Example 1.
//In this example, we use only the FilteredElementCollector to retrieve Wall elements.
IEnumerable walls = new FilteredElementCollector(doc).OfClass(typeof(Wall));
foreach (Element item in walls)
{
ElementId id = item.Id;
}

//Example 2.
//Here, we use both the FilteredElementCollector and the ToElements Method to collect Wall elements.
IList wallList = new FilteredElementCollector(doc).OfClass(typeof(Wall)).ToElements();
foreach (Element item in wallList)
{
ElementId id = item.Id;
}

Here is a sample blog where the same has been discussed.

https://thebuildingcoder.typepad.com/blog/2016/04/how-to-distinguish-redundant-rooms.html#2